Systems, methods, apparatuses, and devices for radar-based identifying, tracking, and managing of unmanned aerial vehicles

ABSTRACT

Systems, methods, and apparatus for identifying and tracking UAVs including a plurality of sensors operatively connected over a network to a configuration of software and/or hardware. Generally, the plurality of sensors monitors a particular environment and transmits the sensor data to the configuration of software and/or hardware. The data from each individual sensor can be directed towards a process configured to best determine if a UAV is present or approaching the monitored environment. Radar sensors included in the plurality of sensors may identify specific locations corresponding to objects in an airspace, and video sensors such as PTZ cameras may be directed to collect image data of the objects at the specific locations for identifying the objects as UAVs and tracking the UAVs. The system predicts next locations for the UAVs and directs the PTZ cameras to update their orientations for following the UAVs.

TECHNICAL FIELD

The present disclosure relates generally to identifying, tracking, and managing unmanned aerial vehicles using a plurality of sensors, computer hardware, and computer software.

BACKGROUND

Unmanned Aerial Vehicles (UAVs), often referred to as “drones”, are generally aircrafts operated without the presence of a pilot on board. UAVs vary in size and may be controlled in real time from a remote location, or configured to operate autonomously. The introduction and growing popularity of UAVs in the airspace has raised issues regarding government regulations and the allowable usage of UAVs.

The anonymous nature of UAVs has introduced problems in areas where accountability and identity are of the utmost importance. Locations such as airports, prisons, sporting venues, residential homes, etc., are among these areas that require a safe and regulated airspace around their perimeters, and UAVs compromise the ability to ensure the safety of such airspaces.

Conventional systems cannot quickly and accurately identify, track, and monitor the activities of UAVs and other airborne objects. For example, a conventional system may identify an object within an airspace, but may lack the sophistication for classifying the object. Furthermore, conventional systems may require constant human control and input for following an object within an airspace, which often results in losing sight of the object (e.g., the object is too fast or performs maneuvers not anticipated by a human).

Therefore, there is a long-felt but unresolved need for a system, method, apparatus, and/or device that is designed to detect, identify, track, and monitor UAVs in order to better protect airspaces and the areas they surround as well as monitor appropriate UAV operations.

BRIEF SUMMARY OF THE DISCLOSURE

Briefly described, and according to one embodiment, aspects of the present disclosure relate generally to systems, methods, apparatuses, and devices for identifying, tracking, and managing unmanned aerial vehicles (UAVs) using a plurality of sensors, hardware, and software. In one embodiment, and in accordance with aspects of the present disclosure, a plurality of sensors including at least radar, video, audio, Wi-Fi, infrared, and radio frequency (RF) sensors, collect data from their surrounding environment in order to detect, identify, track, and manage UAVs.

In one embodiment, the video sensor is configured to “see” any approaching objects. In various embodiments the video sensor records high definition video and can detect objects approaching from 100 meters away (or other predetermined distances based on technical specifications of the video sensor). According to various aspects of the present disclosure, the audio sensor is configured to “listen” to noise and various frequencies and/or frequency ranges that may be emitted from UAVs. In various embodiments, the Wi-Fi sensor included in the plurality of sensors is configured to detect Wi-Fi signals, and more particularly detect information transmitted within Wi-Fi signals such as SSID's, MAC addresses, and other information. In one embodiment, the RF sensor is configured to monitor frequencies spanning the frequency range of 1 MHz to 6 GHz; however, the RF sensor may be configurable beyond this range in certain embodiments. In some embodiments, included in the RF sensor is at least one software defined radio (SDR) which allows the RF sensor to be dynamically configurable to monitor any RF frequency and/or range within the radio frequency spectrum.

In various embodiments, the systems, methods, apparatuses, and devices described herein collect and process large amounts of sensor information which may allow for the system to not only identify and track UAVs, but also manage a recognizable catalog of UAVs that the system “knows” and monitors.

In certain embodiments, each sensor may collect its respective data and process the data locally within the circuitry of the sensor. In other embodiments, the sensors merely collect the data and forward the data to a central server which then processes the data.

In one embodiment, the present systems, methods, apparatuses, and devices allow for determining the locations (e.g., 3D coordinates) of UAVs (or other objects) in an airspace via radar sensors. As will be understood by one of ordinary skill in the art, a radar sensor may emit a signal (e.g. an electromagnetic wave) in a particular direction, and the radar sensor may later receive the same signal in response to the signal being reflected off of an object. Accordingly, the location of the object can be determined based on the direction of the radar signal (e.g., the orientation of the radar sensor) and the elapsed time between initially emitting the signal to receiving the reflected signal. In various embodiments, a radar sensor may not immediately be able to verify or classify an object detected in an airspace. Thus, in at least one embodiment, the disclosed system may further leverage sensors such as pan, tilt, and zoom cameras (“PTZ” cameras, or simply “PTZs”) or radio frequency (“RF”) sensors (and other sensors) for verifying that an object detected via a radar sensor is, or is not, a UAV.

As will be described in greater detail herein, the system may maintain records of objects identified via radar sensors (or other sensors), where these records include object “tracks.” In particular embodiments, tracks include a plurality of sensor readings and associated data that define an objects trajectory (historical and predicted) through a 3D space. In certain embodiments, tracks generally start from an initially detected location (e.g., a “tail”) and continue to move through an airspace. According to various aspects of the present disclosure, tracks include stored 3D coordinates corresponding to radar readings, thus allowing the system to generate 3D models based on the stored 3D coordinates for predicting track behavior. For example, if a particular track includes a series of radar readings indicating an object traveling along a particular path or arc, the system may predict (within a certain confidence/certainty) subsequent radar readings corresponding to the object along the track. The system may also calculate a velocity and/or acceleration for the particular track based on the stored 3D coordinates (or other sensor readings).

In various embodiments, the most recently detected position of an object track may be the track's “head,” and newly received radar readings are compared to known tracks for determining to which track the identified object may belong. In certain embodiments, if a radar reading cannot be confidently associated with a preexisting track (e.g., the newly received radar reading is not located near any known track), the system may create a new track.

In at least one embodiment, the records of identified objects may furthermore include a total or average amount of time spent by the system verifying the detected objects via other sensors such as PTZ cameras or RF sensors. In certain embodiments, the records of identified objects may include a time threshold (e.g., a predetermined time threshold or a dynamic time threshold that changes based on system parameters), where the time threshold indicates an acceptable time spent for verifying tracks. In particular embodiments, the system may include a certain number of PTZ cameras, and each PTZ camera may only track one object at a time. Thus, in an example scenario, when determining for which tracks to verify or confirm a UAV presence, the system may prioritize certain tracks with generally low time spent, such that these tracks are already likely to include a UAV and can be more easily verified. In other embodiments, the time counter may be a global variable used for determining if too much time is being spent by one particular PTZ for verifying a track. Accordingly, if it is determined that too much time is being spent verifying a particular track (e.g., significantly more time spent as compared to other tracks), it may be determined that the track is unlikely to include a UAV, the track may be dismissed, and the PTZ camera (or other sensor) may be reassigned to another track.

According to various aspects of the present disclosure, the PTZ cameras assigned to particular tracks may be configured to automatically follow the object associated with the track based on location predictions and additional radar readings. In some embodiments, the system may follow tracks with only PTZ cameras, if, for example, the PTZs maintain the track within (or near) their field of view. In at least one embodiment, the system may direct a PTZ camera's orientation towards the location of an object detected via radar, and in response to detecting the tracked object via the PTZ camera, the system may continue to calculate predicted positions of the object based on detected velocity, acceleration, size, movement patterns, etc., and use these calculated predictions for determining the PTZ camera's next orientation for continuing to follow the object. In various embodiments, the system may continuously re-orient the PTZ cameras based on predicted track object movements and actual detected track object movements, to maintain the object in the center (or near center) of the PTZ field of view (e.g., image frame).

In one embodiment, the present disclosure discusses a system for identifying unmanned aerial vehicles (UAVs) in a particular airspace, the system including: a radar sensor configured to monitor the particular airspace; a plurality of image capturing devices physically proximate to the radar sensor and configured to monitor the particular airspace; and a server including a processor, wherein the server is operatively connected to the radar sensor and the plurality of image capturing devices, and wherein the processor is operative to: receive signal readings from the radar sensor, wherein the signal readings include location data corresponding to one or more objects detected in the particular airspace via the radar sensor; compare the received signal readings to a plurality of historical readings, wherein the plurality of historical readings correspond to known object trajectories detected within the particular airspace, and wherein each of the plurality of historical readings includes a predicted location of an object and an acceptable location uncertainty corresponding to a subsequent object location; and upon determining that a particular reading of the received signal readings includes location data substantially similar to the predicted location of a matching historical reading and is within the acceptable location uncertainty corresponding to the matching historical reading, associate the particular reading with the matching historical reading.

In various embodiments, associating includes adding the particular reading to the matching historical reading. In particular embodiments, the processor is further operative to determine, for the matching historical reading, a particular image capturing device of the plurality of image capturing devices to be assigned to the matching historical reading, wherein determining includes evaluating at least the location data corresponding to the matching historical reading to locations of each of the plurality of image capturing devices. In certain embodiments, the processor is further operative to direct the particular image capturing device to monitor the particular airspace corresponding to the location data of the matching historical reading. Furthermore, according to various aspects of the present disclosure, the processor is further operative to receive image data from the particular image capturing device, wherein the image data depicts the particular airspace corresponding to the location data for verifying the one or more objects as UAVs.

In one embodiment, the processor directs the particular image capturing devices via a PID controller. In certain embodiments, the PID controller is adjusted at about 30 cycles per second. In a particular embodiment, the processor is further operative to perform an object detection process in response to receiving the image data. In various embodiments, the plurality of historical readings are associated with a track including a record of three-dimensional coordinates corresponding to the known object trajectories detected within the particular airspace, and the predicted location of the object, and each of the plurality of historical readings includes a timer for recording time spent verifying the one or more objects as UAVs.

According to various aspects of the present disclosure, determining assignments includes evaluating the timer at the matching historical reading. In one embodiment, the processor calculates a new predicted location for the matching historical reading in response to adding the particular reading to the matching historical reading. In various embodiments, each of the image capturing devices include pan-tilt-zoom (“PTZ”) cameras. In some embodiments, the acceptable location uncertainty is about 70% certain.

In particular embodiments, the present disclosure discusses a method for identifying unmanned aerial vehicles (UAVs) in a particular airspace via a processor at a server, wherein the server is operatively connected to a radar sensor configured to monitor the particular airspace, and operatively connected to a plurality of image capturing devices physically proximate to the radar sensor and configured to monitor the particular airspace, the method including the steps of: receiving signal readings from the radar sensor, wherein the signal readings include location data corresponding to one or more objects detected in the particular airspace via the radar sensor; comparing the received signal readings to a plurality of historical readings, wherein the plurality of historical readings correspond to known object trajectories detected within the particular airspace, and wherein each of the plurality of historical readings includes a predicted location of an object and an acceptable location uncertainty corresponding to a subsequent object location; and upon determining that a particular reading of the received signal readings includes location data substantially similar to the predicted location of a matching historical reading and is within the acceptable location uncertainty corresponding to the matching historical reading, associating the particular reading with the matching historical reading.

In one embodiment, associating includes adding the particular reading to the matching historical reading. In a particular embodiment, the method further includes the step of determining, for the matching historical reading, a particular image capturing device of the plurality of image capturing devices to be assigned to the matching historical reading, wherein determining includes evaluating at least the location data corresponding to the matching historical reading to locations of each of the plurality of image capturing devices. In a certain embodiments, the method further includes the step of directing the particular image capturing device to monitor the particular airspace corresponding to the location data of the matching historical reading.

In at least one embodiment, the method further includes the step of receiving image data from the particular image capturing device, wherein the image data depicts the particular airspace corresponding to the location data for verifying the one or more objects as UAVs. In certain embodiments, the processor directs each of the particular image capturing device via a PID controller, and the PID controller is adjusted at about 30 cycles per second.

In a particular embodiment, the processor is further operative to perform an object detection process in response to receiving the image data. In one embodiment, the plurality of historical readings are associated with a track including a record of three-dimensional coordinates corresponding to the known object trajectories detected within the particular airspace, and the predicted location of the object. In certain embodiments, each of the plurality of historical readings includes a timer for recording time spent verifying the one or more objects as UAVs. In some embodiments, determining assignments includes evaluating the timer at the matching historical reading. According to various aspects of the present disclosure, the processor calculates a new predicted location for the matching historical reading in response to adding the particular reading to the matching historical reading. Furthermore, in various embodiments, each of the image capturing devices include pan-tilt-zoom (“PTZ”) cameras. In certain embodiments, the acceptable location uncertainty is about 70% certain.

These and other aspects, features, and benefits of the claimed invention(s) will become apparent from the following detailed written description of the preferred embodiments and aspects taken in conjunction with the following drawings, although variations and modifications thereto may be effected without departing from the spirit and scope of the novel concepts of the disclosure.

BRIEF DESCRIPTION OF FIGURES

The accompanying drawings illustrate one or more embodiments and/or aspects of the disclosure and, together with the written description, serve to explain the principles of the disclosure. Wherever possible, the same reference numbers are used throughout the drawings to refer to the same or like elements of an embodiment, and wherein:

FIG. 1 is an exemplary operational environment, according to one embodiment of the present disclosure;

FIG. 2 is an exemplary portrayal of ranges of a plurality of sensors, according to one embodiment of the present disclosure;

FIG. 3 illustrates a top plan view of a structure with a plurality of deployed sensors covering a range around the structure, according to one embodiment of the present disclosure;

FIG. 4 illustrates exemplary system architecture, according to one embodiment of the present disclosure;

FIG. 5A is an exemplary sensor device, according to one embodiment of the present disclosure;

FIG. 5B is an exemplary RF sensor device, according to one embodiment of the present disclosure;

FIG. 6 is a flowchart illustrating the general main flow process of the system, according to one embodiment of the present disclosure;

FIG. 7 is a flowchart illustrating the video data analysis process, according to one embodiment of the present disclosure;

FIG. 8 is a representative frame from the video data analysis process, according to one embodiment of the present discourse;

FIG. 9 is a flowchart illustrating the scene learning process, according to one embodiment of the present disclosure;

FIG. 10 is a flowchart illustrating the object classification process, according to one embodiment of the present disclosure;

FIG. 11 is a flowchart illustrating the audio data analysis process, according to one embodiment of the present disclosure;

FIG. 12 is a flowchart illustrating the radio frequency data analysis process, according to one embodiment of the present disclosure;

FIG. 13 is a flowchart illustrating the Wi-Fi data analysis process, according to one embodiment of the present disclosure;

FIG. 14 is a flowchart illustrating the general region of interest tracking process, according to one embodiment of the present disclosure;

FIG. 15 is a diagram illustrating an exemplary airspace and track, according to one embodiment of the of the present disclosure;

FIG. 16 is a flowchart of an exemplary track initialization process, according to one embodiment of the present disclosure;

FIG. 17 is a flowchart of an exemplary track verification via PTZ camera process, according to one embodiment of the present disclosure;

FIG. 18 is a flowchart of an exemplary PTZ camera assignment process, according to one embodiment of the present disclosure; and

FIG. 19 is a flowchart of an exemplary PTZ tracking process, according to one embodiment of the present disclosure.

DETAILED DESCRIPTION OF FIGURES

For the purpose of promoting an understanding of the principles of the present disclosure, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same. It will, nevertheless, be understood that no limitation of the scope of the disclosure is thereby intended; any alterations and further modifications of the described or illustrated embodiments, and any further applications of the principles of the disclosure as illustrated therein are contemplated as would normally occur to one skilled in the art to which the disclosure relates. All limitations of scope should be determined in accordance with and as expressed in the claims.

One embodiment of the present disclosure generally relates to systems, methods, apparatuses, and devices configured to identify, track, and manage UAVs. These and other aspects, features, and benefits of the claimed invention(s) will become apparent from the following detailed written description of the preferred embodiments and aspects taken in conjunction with the following drawings, although variations and modifications thereto may be effected without departing from the spirit and scope of the novel concepts of the disclosure.

Briefly described, and according to one embodiment, aspects of the present disclosure relate generally to systems, methods, apparatuses, and devices for identifying, tracking, and managing unmanned aerial vehicles (UAVs) using a plurality of sensors, hardware, and software. In one embodiment, and in accordance with aspects of the present disclosure, a plurality of sensors including at least radar, video, audio, Wi-Fi, infrared, and radio frequency (RF) sensors, collect data from their surrounding environment in order to detect, identify, track, and manage UAVs.

In one embodiment, the video sensor is configured to “see” any approaching objects. In various embodiments the video sensor records high definition video and can detect objects approaching from 100 meters away (or other predetermined distances based on technical specifications of the video sensor). According to various aspects of the present disclosure, the audio sensor is configured to “listen” to noise and various frequencies and/or frequency ranges that may be emitted from UAVs. In various embodiments, the Wi-Fi sensor included in the plurality of sensors is configured to detect Wi-Fi signals, and more particularly detect information transmitted within Wi-Fi signals such as SSID's, MAC addresses, and other information. In one embodiment, the RF sensor is configured to monitor frequencies spanning the frequency range of 1 MHz to 6 GHz; however, the RF sensor may be configurable beyond this range in certain embodiments. In some embodiments, included in the RF sensor is at least one software defined radio (SDR) which allows the RF sensor to be dynamically configurable to monitor any RF frequency and/or range within the radio frequency spectrum.

In various embodiments, the systems, methods, apparatuses, and devices described herein collect and process large amounts of sensor information which may allow for the system to not only identify and track UAVs, but also manage a recognizable catalog of UAVs that the system “knows” and monitors.

In certain embodiments, each sensor may collect its respective data and process the data locally within the circuitry of the sensor. In other embodiments, the sensors merely collect the data and forward the data to a central server which then processes the data.

In one embodiment, the present systems, methods, apparatuses, and devices allow for determining the locations (e.g., 3D coordinates) of UAVs (or other objects) in an airspace via radar sensors. As will be understood by one of ordinary skill in the art, a radar sensor may emit a signal (e.g. an electromagnetic wave) in a particular direction, and the radar sensor may later receive the same signal in response to the signal being reflected off of an object. Accordingly, the location of the object can be determined based on the direction of the radar signal (e.g., the orientation of the radar sensor) and the elapsed time between initially emitting the signal to receiving the reflected signal. In various embodiments, a radar sensor may not immediately be able to verify or classify an object detected in an airspace. Thus, in at least one embodiment, the disclosed system may further leverage sensors such as pan, tilt, and zoom cameras (“PTZ” cameras, or simply “PTZs”) or radio frequency (“RF”) sensors (and other sensors) for verifying that an object detected via a radar sensor is, or is not, a UAV.

As will be described in greater detail herein, the system may maintain records of objects identified via radar sensors (or other sensors), where these records include object “tracks.” In particular embodiments, tracks include a plurality of sensor readings and associated data that define an objects trajectory (historical and predicted) through a 3D space. In certain embodiments, tracks generally start from an initially detected location (e.g., a “tail”) and continue to move through an airspace. According to various aspects of the present disclosure, tracks include stored 3D coordinates corresponding to radar readings, thus allowing the system to generate 3D models based on the stored 3D coordinates for predicting track behavior. For example, if a particular track includes a series of radar readings indicating an object traveling along a particular path or arc, the system may predict (within a certain confidence/certainty) subsequent radar readings corresponding to the object along the track. The system may also calculate a velocity for the particular track based on the stored 3D coordinates (or other sensor readings).

In various embodiments, the most recently detected position of an object track may be the track's “head,” and newly received radar readings are compared to known tracks for determining to which track the identified object may belong. In certain embodiments, if a radar reading cannot be confidently associated with a preexisting track (e.g., the newly received radar reading is not located near any known track), the system may create a new track.

In at least one embodiment, the records of identified objects may furthermore include a total or average amount of time spent by the system verifying the detected objects via other sensors such as PTZ cameras or RF sensors. In certain embodiments, the records of identified objects may include a time threshold (e.g., a predetermined time threshold or a dynamic time threshold that changes based on system parameters), where the time threshold indicates an acceptable time spent for verifying tracks. In particular embodiments, the system may include a certain number of PTZ cameras, and each PTZ camera may only track one object at a time. Thus, in an example scenario, when determining for which tracks to verify or confirm a UAV presence, the system may prioritize certain tracks with generally low time spent, such that these tracks are already likely to include a UAV and can be more easily verified. In other embodiments, the time counter may be a global variable used for determining if too much time is being spent by one particular PTZ for verifying a track. Accordingly, if it is determined that too much time is being spent verifying a particular track (e.g., significantly more time spent as compared to other tracks), it may be determined that the track is unlikely to include a UAV, the track may be dismissed, and the PTZ camera (or other sensor) may be reassigned to another track.

According to various aspects of the present disclosure, the PTZ cameras assigned to particular tracks may be configured to automatically follow the object associated with the track based on location predictions and additional radar readings. In some embodiments, the system may follow tracks with only PTZ cameras, if, for example, the PTZs maintain the track within (or near) their field of view. In at least one embodiment, the system may direct a PTZ camera's orientation towards the location of an object detected via radar, and in response to detecting the tracked object via the PTZ camera, the system may continue to calculate predicted positions of the object based on detected velocity, acceleration, size, movement patterns, etc., and use these calculated predictions for determining the PTZ camera's next orientation for continuing to follow the object. In various embodiments, the system may continuously re-orient the PTZ cameras based on predicted track object movements and actual detected track object movements, to maintain the object in the center (or near center) of the PTZ field of view (e.g., image frame).

Referring now to the figures, for the purposes of example and explanation of the fundamental processes and components of the disclosed systems, methods, apparatuses, and devices, reference is made to FIG. 1 , which illustrates an exemplary, high-level overview of one embodiment of an operational environment 100 in accordance with various aspects of the present disclosure. As will be understood and appreciated, the conceptual overview shown in FIG. 1 represents merely one approach or embodiment of the present system, and other aspects are used according to various embodiments of the present system.

In one embodiment, the exemplary operational environment 100 includes at least an Unmanned Aerial Vehicle Tracking and Monitoring System (UAVTMS) 102 and a plurality of installation locations 110A, 110B, and 110C. In various embodiments, the UAVTMS 102 is a central system combined with a plurality of sensors and other computer hardware and software operating to identify, track, and manage UAVs. According to various aspects of the present disclosure, the UAVTMS 102 may be referred to herein as the central system or the central system and sensors. In particular embodiments, the central system is configured to accept data from the plurality of sensors indicated throughout as element 112, as well as various computing devices, databases, and other external sources of electronic data. The UAVTMS 102 may be further configured to process the various sensor readings and other data through a series of algorithms and computer implemented processes to identify, track, and manage UAVs. In general, all information from the installation locations may be directed to the central system of the UAVTMS 102 for processing and in some embodiments the UAVTMS 102 may convert the information from the external environments into meaningful data that can be used to further identify and track UAVs.

The disclosed systems, methods, apparatuses, and devices may be desirable in many situations and scenarios. For example, buildings and structures such as government buildings, prisons, universities, airports, sporting venues, personal homes, etc., require a safe and monitored airspace as well as surrounding area. The UAVTMS 102 disclosed herein may allow a plurality of sensors to monitor the airspace and general area surrounding buildings and structures, such as the buildings and structures mentioned above. Further, as UAVs continue to become more popular and acceptable in society, it may be desirable to be able to distinguish malicious UAVs (UAVs for spying, trespassing, etc.) from benign UAVs (UAVs for delivering consumer goods, etc.). In one embodiment, the UAVTMS 102 disclosed herein may be configured to monitor particular UAVs and store information regarding particular malicious and benign UAVs in order to better identify, monitor, and manage their presence in an airspace.

In some embodiments, the UAVTMS 102 may include at least a management module 104 and a database 106. As will be described in further detail in FIG. 4 , the management module 104 may execute the computer implemented methods of processing data inputs and outputs, as well as analyzing whether or not an object is a UAV and further determine if it should be tracked, monitored, or otherwise responded to in another appropriate manner. The management module 104 may include hardware components such as a processor, computer executable instructions, a non-transitory computer readable medium wherein the computer executable instructions may be stored, etc. In the present embodiment, the management module 104 may share a bi-directional communication link with a database 106 which may allow for the two elements to send and receive data across the communication link as necessary. The database 106 included in the UAVTMS 102 may store any information pertaining to the processes performed by the management module 104. Examples of this information may include but are not limited to images of previously identified UAVs, audio files including data representing sound patterns of UAVs, information about objects that resemble UAVs but should not be mistaken for one, etc. According to various aspects of the present disclosure, the central system of the UAVTMS 102 may include modules such as the management module 104. Also, the management module 104 may include various servers, databases, and other computing hardware located either in a remote or central location. In one embodiment, the central system may operate as a cloud computing system. In other embodiments, the central system may be physically located in close proximity to the installation locations.

Continuing with FIG. 1 and as mentioned above, in some embodiments the UAVTMS 102 may be deployed at a plurality of installation locations, indicated throughout as 110A-110C, through networks 108. The networks 108 may be, but are not limited to the Internet, and may involve the usage of one or more services (e.g., a Web-deployed service with client/service architecture, a corporate Local Area Network (LAN) or Wide Area Network (WAN), a cellular data network, or through a cloud-based system). Moreover, as will be understood and appreciated by one having ordinary skill in the art, various networking components like routers, switches, hubs, etc. are typically involved in these communications. Although not shown in FIG. 1 , such communications may include, in various embodiments, one or more secure networks, gateways, or firewalls that provide additional security from unwarranted intrusions by unauthorized third parties and cyber-attacks.

As shown in the present embodiment, examples of installation locations may include airports 110A, prisons 110B, and residential homes 110C, whereby the installation locations 110A-110C may send and receive data over networks 108 to the central system of the UAVTMS 102. In some embodiments, the installation locations 110A-110C may provide the majority of data accepted by the UAVTMS 102. It should be understood by the discussion herein that the present disclosure should not be limited to installation locations described.

According to aspects of the present disclosure, the installation locations such as airports 110A, prisons 110B, residential homes 110C, or other structures and buildings may include a plurality of sensors 112A-112C deployed on the structure or building that communicate with the central server of the UAVTMS 102 over a network 108. In some embodiments, the plurality of sensors may communicate the sensor readings, over the network 108, to the UAVTMS 102 to be processed. In other embodiments, the sensor readings may be processed locally before being sent to the UAVTMS 102. In an example scenario, a UAV may be approaching a fenced enclosure adjacent to a prison 110B. This scenario may present a risk to the prison 110B, because the UAV may be carrying a payload that could be dangerous if it were to be delivered to a prison inmate. The plurality of sensors 112B deployed on the prison 110B may identify and track the UAV before it has the opportunity to drop the payload onto prison grounds or present a risk in another situation. In one embodiment, the UAVTMS 102 may identify and track the approaching UAV and alarm the prison guards to escort any inmates back into the prison 110B. In another embodiment, the prison 110B may exercise forceful action against the UAV, which may include overtaking the UAV's control system or disabling the UAV's ability to remain airborne. In other embodiments, the central system of the UAVTMS 102 operating at the prison 110B may simply track the UAV, and manage the UAV's identity within the central system of the UAVTMS in order to more easily recognize the UAV if it were to re-appear in the future.

In various embodiments, the sensors included in the plurality of sensors 112A-112C may be proprietary sensors or commercially available sensors. In particular embodiments, the video sensor included in the plurality of sensors 112A-112C is similar to the Lensation GmbH Lensagon B10M5425. In one embodiment, the video sensor has a dome-shaped configuration and is capable of recording 1080p resolution video within a wide angled field of view. According to various aspects of the present disclosure, the video sensor is configured to record activity within a field of view that a UAV would be expected to enter. For example, the video sensor may be pointed upward at the sky in anticipation of a UAV approaching from a high altitude. In some embodiments, a pre-installed stand-alone video sensor, such as pre-existing home/location security equipment, can be included in the plurality of sensors 112A-112C. In other embodiments, video sensors included in the plurality of sensors 112A-112C may be pan-tilt-zoom (“PTZ”) cameras with functionality similar to the LZV2925B model camera manufactured and sold by Lorex Technology, and other makes/models as well. According to various aspects of the present disclosure, the PTZ cameras may periodically scan the airspace for detecting UAVs, or the PTZ cameras may be directed to a particular location in the airspace for visually confirming that a detected object is indeed a UAV.

In various embodiments, the audio sensor may be a proprietary waterproof audio sensor designed to receive, amplify, and convert sound from audible vibrations to digital representations of a signal by implementing an analog to digital converter. According to various aspects of the present disclosure, the audio sensor may be capable of 24-bit sampling at various rates, such as 192 kHz.

In one embodiment, the Wi-Fi sensor may operate similarly to the Intel Corporation Dual Band Wireless-AC 3160 Wi-Fi card. In various embodiments, the Wi-Fi sensor is configured to detect wireless signals and more particularly Wi-Fi signals transmitting information such as Service Set Identifiers (SSID), Media Access Control (MAC) addresses, Received Signal Strength Indicators (RSSI), and other information regarding potential UAVs.

In various embodiments, the RF sensor may operate similarly to the Great Scott Gadgets HackRF One sensors. In various embodiments, the RF sensor is configurable to operate within the 1 MHz to 6 GHz frequency range. In particular embodiments, the RF sensor may be configured to operate within any appropriate frequency range as defined by the particular hardware and software in operating on the device.

According to various aspects of the present disclosure, the plurality of sensors 112A-112C may include one or more radar sensors. In certain embodiments, the radar sensors included in the plurality of sensors 112A-112C may be capable of detecting objects in an airspace at ranges of 250 meters or more, and one radar sensor may be operable to detect a plurality of objects (e.g., two, five, twenty-five objects, etc.). In particular embodiments, the system may include radar sensors similar to the R8SS manufactured by FLIR Systems in Wilsonville, Oreg., U.S., and also radar sensors similar to the MESA 700-00050203_SSR manufactured by Echodyne Corp. in Kirkland, Wash., U.S.

In one embodiment, a user 118 operates a computing device connected to the central system of the UAVTMS 102 over the network 108. According to various aspects of the present disclosure, the user 118 may be a moderator or manager of a particular installation location 110A-110C. In some embodiments, the user 118 may be able to interact with or monitor the plurality of sensors 112A-112C at the installation locations 110A-110C. In an example scenario, a user may have a plurality of sensors 112C deployed on his/her home 110C and would like to monitor his/her surrounding property while away. Using a computing device such as a mobile phone, the user 118 could access the information regarding the plurality of sensors 112C deployed on his/her home 110C by logging into the central system of the UAVTMS 102 and accessing a control panel or dashboard. In various embodiments, accessing the control panel or dashboard allows for the user 118 to manage the plurality of sensors 112C at the installation location 110C as well as view real-time feeds from the video sensor, historical data from previous UAVs or non-UAVs that were detected by the central system and sensors 102, current maps representing particular sensor ranges, individual sensor diagnostics, and other relevant information regarding the identifying, tracking, monitoring, and managing of UAVs. In particular embodiments, there may be multiple deployments of a plurality of sensors 112C on the installation location 110C. In accordance with aspects of the present disclosure, the user 118 may manage multiple deployments of sensors 112C on one installation location 110C from the portal or dashboard. Also, the user 118 may manage multiple installation locations 110C from the portal or dashboard.

In some embodiments, the user 118 may use a computing device in order to access a web server or web application that may allow access to the central system of the UAVTMS 102. It should be understood from the discussion herein that any type of computing device such as a tablet, laptop computer, desktop computer, mobile phone, etc., could be used to access the central system of the UAVTMS 102 and the present disclosure should not be limited to the use of just a mobile phone.

In one embodiment, third party databases and data sources 120 are connected to the central system of the UAVTMS 102 over a network 108. These third party databases 120 may include a plurality of different datasets and sources of information pertinent to identifying and tracking UAVs, or maintaining a system as described in the present disclosure. As necessary, the central system of the UAVTMS 102 may write and read data to and from the third party databases 120. In various embodiments, it may be beneficial for the central system of the UAVTMS 102 to access information regarding UAV manufacturers and specifications in a third party database 120 in order to cross reference and verify the data collected by the plurality of sensors 112A-112C with the manufacturer's information. In a scenario where a UAV is approaching an airport 110A and the airport 110A has deployed a plurality of sensors 112A such as those described herein, the plurality of sensors 112A may be able to read signals from the approaching UAV and compare them to signals known to be emitted from certain UAVs of particular manufacturers. In other embodiments, the plurality of sensors 112A may transmit the detected signals to the central system of the UAVTMS 102 in order to compare the signals to other signal known to be emitted from certain UAVs of particular manufacturers. That information may allow the airport 110A to make an informed decision regarding how to respond to the approaching UAV. In some embodiments, information similar to the information available from third party databases 120 may already be stored in a database 106 included in the UAVTMS 102. However, including access to third party databases 120 may allow for the UAVTMS 102, as well as all parts of the disclosed system, to have access to the most recent information available in real time.

In the present embodiment, a third party database 120 is shown including relevant data and information 122 corresponding to but not limited to UAV updates, regulations, manufacturer specifications, and other general information. In one embodiment, this relevant data and information 122 may allow for the central system of the UAVTMS 102 to have access to data that may determine how the system may respond to UAVs. For example, the Federal Aviation Administration (FAA) may release new regulations regarding how UAVs may be operated in certain areas. This information may then automatically be updated in the third party database 120. This updated information may change how the system responds to a detected UAV flying at a certain height if operating a UAV at that height is made illegal based on new regulations.

In various embodiments, the relevant data and information 122 may include information pertaining to particular UAVs such as MAC addresses, particular communication frequencies, noise patterns, and other manufacturer-specific information regarding UAVs. By accessing the data and information 122 included in the third party database 120, the central system of the UAVTMS 102 may be able to more consistently and accurately identify, track, monitor, and manage UAVs.

Still referring to FIG. 1 , in one embodiment, the plurality of sensors 112A-112C may be combined into one all-encompassing device. Devices such as those shown in FIGS. 5A and 5B may include the plurality of sensors 112A-112C described in the discussion herein. According to various aspects of the present disclosure, the plurality of sensors 112A-112C may be a single sensor or many sensors enclosed in either one more multiple devices. Now referring back to FIG. 1 , a device 112A may be installed on the air traffic control tower of the airport 110A in the present embodiment. In one embodiment, a device range 114A, represented as dotted lines and propagating from the device 112A, indicates the range that the device 112A may be able to detect UAVs within. In various embodiments, having a plurality of sensors included in one device may allow the ranges of each sensor to originate from the same location. In some embodiments, it may be beneficial to have a plurality of sensors included in one device and other sensors as stand-alone sensors if a particular area needs specific or customized coverage. In particular embodiments, the airport 110A may require multiple devices 112A in order to sufficiently cover a desired area or range. According to various aspects of the present disclosure, any appropriate sensor may be included in the device 112A, and the present disclosure should not be limited to the sensors listed and described.

In the present embodiment and continuing with the airport 112A external environment, a UAV 116A is shown within the dotted lines representing the device range 114A. According to aspects of the present disclosure, the UAV 116A may be detectable by one or more sensors included within the device 112A when the UAV 116A enters the device range 114A. Once within the device range 114A, the device 112A may transmit information regarding the UAV 116A to the central system of the UAVTMS 102 for processing. In certain embodiments, the device 112A may process the sensor readings locally. Once the information regarding the UAV 116A is processed by the UAVTMS 102, the UAVTMS 102 may then decide how to respond to the UAV 116A. Also in the present embodiment is an airplane 118A flying near the airport 110A. In one embodiment, the airplane 118A may enter a device range 114A. Similarly to when the UAV 116A enters the device range 114A, when the airplane 118A enters the device range 114A the device 112A may transmit information regarding the airplane 118A to the central system of the UAVTMS 102 for processing, or the processing may occur locally at the device 112A. As will be discussed in greater detail herein, when the UAV 116A and the airplane 118A are detected within the device range 114A, the central system and sensors in general do not know or have not confirmed the identity of these objects, but the UAVTMS 102 can quickly identify each object as a UAV or non-UAV by implementing the various systems and methods described in the present disclosure.

Continuing with FIG. 1 and according to aspects of the present disclosure, the devices 112A-112C can be used in many environments and installation locations in addition to those discussed herein. In various embodiments, devices such as 112A-112C may be deployed at locations such as hospitals, office buildings, universities, sporting venues, etc.

Turning now to FIG. 2 , an exemplary portrayal 200 of sensor ranges around a location (e.g., an airport 110A) is shown according to one embodiment of the present disclosure. In the present embodiment, a RF sensor range 202A, video sensor range 202B, Wi-Fi sensor range 202C, and an audio sensor range 202D surround the airport 110A and may be propagated from a device 112A including the sensors. In various embodiments, a radar sensor may include a range similar to that of the RF sensor range 202A. In the present embodiment, the device 112A is shown included on the air traffic control tower, but it should be understood from the discussion herein that the device 112A, or many devices 112A, may be deployed anywhere in or around the airport 110A. As will be described further below in the detailed description of FIG. 2 , combining data from a plurality of sensors allows for the UAVTMS 102 to quickly identify a UAV in an area that may contain various non-UAV objects such as birds and planes that may trigger typical aerial monitoring devices.

In an environment such as the one shown in the present embodiment, it may be important to monitor and control the surrounding airspace. A situation may arise where a UAV is flying near the airport 110A runway and may strike an airplane, potentially causing damage to the airplane and risking the lives of the passengers. Another situation may arise where a particular military aircraft is intended to remain concealed within the confines of the airport 110A, and a UAV equipped with a camera may recognize the aircraft, resulting in a national security threat. In one embodiment, the RF, video, Wi-Fi, radar, and audio sensors may all be configured to monitor their surroundings and prevent the above scenarios. For example, in the present embodiment a UAV 204A has entered the RF sensor range 202A, and therefore the UAV 204A may be detectable by the RF sensor. Also in the present embodiment, a UAV 204C has entered the RF sensor range 202A, video sensor range 202B, and the Wi-Fi sensor range 202C Wi-Fi, and therefore the UAV 204C may be detectable by each of those three sensors. In particular embodiments, if an object is detectable by multiple sensors, it may allow for the UAVTMS 102 to determine if it is a UAV faster than if the object was only detected by one sensor. According to various aspects of the present disclosure, each sensor is capable of monitoring the airspace between the sensor and its farthest extendable range.

In various embodiments, not all types of sensors are capable of extending equivalent ranges. According to aspects of the present disclosure, the ranges of the plurality of sensors may overlap until each sensor has reached it maximum range. For example, in the present embodiment, only the RF sensor and radar sensor are capable of detecting UAVs at its outermost range 202A, and all deployed sensors are capable of detecting UAVs at the audio sensor's outermost range 202D. In particular embodiments, overlapping sensor ranges may allow for the central system and sensors 102 to better identify and determine a UAV from a non-UAV such as a plane or a bird. However, according to various aspects of the present disclosure, the sensor ranges 202A-202D are not required to overlap, and some areas may be better monitored by using one particular sensor. In various embodiments, the described sensor ranges 202A-202D may vary from the current embodiment. For example, it is possible that the audio sensor range 202D may extend farther than the Wi-Fi range 202C based on configuration, hardware specifications, etc. Also, in one embodiment the video sensor may be configured to accept different lenses. Allowing the video sensor to accept different lenses may allow for the video sensor to record a larger field of view, record with increased clarity/resolution at farther distances, etc. In particular embodiments, certain sensor configurations allow for a wide spherical or dome-like range, while other sensor configurations monitor a more directed field of view. The present embodiment is only one configuration of sensor ranges and it should be understood from the discussion herein that there may be many configurations of different sensors and sensor ranges, and the examples shown herein are exemplary and for the purpose of discussion only.

FIG. 3 is a top plan view 300 of multiple buildings or structures at the prison installation location 110B with a plurality of devices 112B deployed thereon. In the present embodiment, the range 114B and direction of the sensor coverage is indicated by dashed lines propagating from the devices 112B. In one embodiment, this range 114B and direction may represent the area around a building or structure at the installation location 110B in which a UAV would be detectable. In some embodiments, each device 112B may be installed at certain angles and configurations in order to monitor a range 114B or a particular field of view or area. In particular embodiments, devices 112B are configured to monitor certain ranges 114B by taking into account vulnerable areas such as large open spaces around the installation location 110B, and other factors such as particular shapes and sizes of buildings in order to ensure that unnecessary amounts of coverage are not directed at locations that require less coverage, etc. According to the present embodiment, each device 112B may have a general range 114B, indicated by the dotted lines propagating from the devices 112B, wherein if a UAV were to enter then that UAV would be detectable. As mentioned previously in FIG. 2 , each device 112B may be configured to include different sensors and different ranges 114B. This is shown, according to one embodiment, by the various device ranges 114B shown in the present embodiment. In various embodiments, one device range 114B may be twice as large as another device range 114B due to either particular configurations, the number of sensors included in the device 112B, the quality and specifications of the particular sensors included, etc. These devices 112B may have been configured to monitor particular areas surrounding the structures 110B in such a way that the area of coverage of all ranges 114B may be maximized. In various embodiments, by strategically choosing the location of installation for each device 112B, the coverage range may be optimized. According to various aspects of the present disclosure, the device ranges 114B may overlap and are not limited to a configuration of ranges such as the ranges shown in the present embodiment.

Referring now to FIG. 4 , an exemplary system architecture 400 is shown, according to one aspect of the present disclosure. In the present embodiment, the central system and sensors of the UAVTMS 102 are illustrated sharing a connection over a network 108. In greater detail, the sensors of the UAVTMS 102 are represented as individual devices 402A-402 n including various numbers of sensors. As previously described in FIG. 1 , a plurality of sensors (e.g., Wi-Fi, video, audio, RF, etc.) may be combined into an all-encompassing device 112, indicated in FIG. 4 as 402A-402 n. The plurality of devices 402A-402 n, each potentially configured to include a certain number of different sensors, may transmit sensor readings to the central system of the UAVTMS 102. In one embodiment, Device 1, indicated as 402A, includes three sensors labeled Sensor 1A, Sensor 1B, and Sensor 1C. It should be understood from the discussion herein that Device 1, indicated as 402A, may include various numbers of sensors of various types (e.g., Wi-Fi, audio, video, RF, radar, etc.). Device 2, indicated as 402B, includes four sensors labeled Sensor 2A, Sensor 2B, Sensor 2C, and Sensor 2D. Device 1, indicated as 402A, may be substantially similar to Device 2, indicated as 402B, minus the one sensor that the two devices may not have in common, as shown in the present embodiment. In the present embodiment, a representation of additional devices, Device “n”, is included and indicated as 402 n. In some embodiments, as many devices as necessary or appropriate may be connected to the central system of the UAVTMS 102 over the network 108. In particular embodiments, the devices 402A-402 n are installed at a plurality of locations which may be remote or local to the central system of the UAVTMS 102. Also operatively connected to the central system of the UAVTMS 102 may be a plurality of computing devices controlled by a user 118 such as, mobile devices 418A, remote servers and systems 418B, and personal computers 418C, etc. As described in FIG. 1 , the computing devices controlled a user 118 may be connected to the central system of the UAVTMS 102 over a network 108 and may be configured to control or monitor the UAVTMS 102 and various locations of the deployed system and sensors, or analyze the information stored within the central system of the UAVTMS 102 by accessing a dashboard or portal. In some embodiments, computing devices such as third party databases 120 are connected to the central system of the UAVTMS 102 and may be configured to operate autonomously.

Continuing with FIG. 4 , an embodiment of the UAVTMS 102 is represented in greater detail than previously shown in FIG. 1 . In the present embodiment, the central system of the UAVTMS 102 includes the management module 104, a Drone/UAV DNA database 412, a system management database 414, and a web server 416 to be described below. In one embodiment, the management module 104 may be configured to intake the sensor information from the devices 402A-402 n as transmitted over the network 108, then process and analyze the information in order to determine how to respond to a detected UAV. In various embodiments, the sensor information from devices 402A-402 n may be processed locally at each device and then only certain results or values may be transmitted over the network 108 to the management module 104. In particular embodiments, the central system of the UAVTMS 102 may be local to the devices 402A-402 n. In these particular embodiments, the processing of the sensor information would be performed locally which may eliminate the need to transmit information. In some embodiments, the data from the devices 402A-402 n may be transmitted to the configuration module 404 represented in the management module 104. According to aspects of the present disclosure, the configuration module 404 may include the processes that interpret and analyze the data from the devices 402A-402 n in order to determine if a UAV is present. The data may then be further transmitted to the module labeled aggregation 406. As will be discussed in greater detail in the discussion of FIG. 6 , the aggregation module 406 may include the processes that combine the results and values, such as confidence levels, from the configuration module 404 in order to determine if a UAV is detected. In the present embodiment, the two modules below the aggregation module 404 are labeled as “actions” 408 and “notifications” 410. In various embodiments, these two modules may represent the processes that determine if a UAV has been identified and how to respond accordingly. For example, processes operating within the aggregation module 406 may combine various confidence levels regarding UAV likelihoods and determine that a UAV is present in a particular area. Further, the processes operating within the actions module 408 may determine that the UAV is an unrecognized UAV and a system moderator should be alerted. Continuing with the example, the processes operating within the actions module 408 may forward the information regarding the identified UAV to the notifications module 410 which may then send an alert regarding the UAV to a user 118 of a user device.

In some scenarios, a particular sensor, such as a Wi-Fi sensor included in the UAVTMS 102, may detect a UAV with 100% (or near 100%) confidence. In this scenario, the configuration module 404 may transmit the information regarding the detected UAV directly to the actions 408 or notifications 410 modules without first transmitting information to the aggregation module 406 because the UAVTMS 102 has already established a 100% (or near 100%) confidence and no further processing is required.

Included in the management module 104 and also connected to by a bi-directional data path are the Drone/UAV DNA database 412 and system management database 414. These databases may include information pertaining to the systems and methods performed within the management module 104. The Drone/UAV DNA database 412 may include information that allows the disclosed system to better identify and track UAVs. In one embodiment, the Drone/UAV DNA database 412 may include meta-information regarding UAVs either compiled over time by the UAVTMS 102 or made available by UAV manufacturers, government agencies, or other organizations. This meta-information may be typical UAV weights, capabilities, and other technical specifications known about particular UAVs. In some embodiments, if a new UAV is detected by the system, the meta-information may be automatically uploaded to the Drone/UAV DNA database 412 to include the new information corresponding to the newly detected UAV. Similarly to the Drone/UAV DNA database 412, in various embodiments the system management database 414 may include information regarding UAV alerts, configurations, or other information regarding general system diagnostics. In particular embodiments, the databases included in the central system of the UAVTMS 102 may include any appropriate information for UAV identification, tracking, and monitoring and should not be limited to the information discussed herein. According to various aspects of the present disclosure, the databases included in the UAVTMS 102 may be cloud based, virtual, local, or any other appropriate form of computer memory.

Continuing with FIG. 4 and in one embodiment, the information stored in the databases 412 and 414, as well as the information processed by the management module 104 may be accessible through a web server 416. The web server 416 may include a bi-directional link between the management module 104, as well as bi-directional links between the at least one database included in the central system of the UAVTMS 102. The web server 416 may also include a bi-directional link and be operatively connected over the network 108 to the plurality of computing devices. In the present embodiment, the plurality of computing devices are indicated as 418A, 418B, and 418C. In the present embodiment, 418A, 418B, and 418C may connect directly to the web server 416 included within the UAVTMS 102. According to aspects of the present disclosure, the web server 416 may allow for the plurality of computing devices 418A, 418B, and 418C to access the data included in the UAVTMS 102. In certain embodiments, it may be useful for the computing devices 418A, 418B and 418C to have access to the web server 416 because the web server 416 may allow the information processed and stored within the UAVTMS 102 to be shared with the users 118 and monitors of the system. In one embodiment, the web server 416 may allow for the plurality of computing devices 418A, 418B, and 418C to access live feeds from sensors. Shown in the present embodiment, the web server 416 includes bi-directional links to all of the elements within the UAVTMS 102. In some embodiments, the web server 416 may handle the querying of information from the UAVTMS 102 and transmitting the queried information to the plurality of computing devices 418A, 418B, and 418C. However, it should be understood from the discussion herein that the computing devices shown in the present embodiment are not intended to limit the scope of the disclosure, rather they are intended to portray the various possible computing devices capable of communicating with the exemplary system.

As will be understood by one of ordinary skill in the art, the system, architectural components, and operative connections/communication pathways shown in these figures are intended to be exemplary only. In various embodiments, the architectural components of the systems and methods described herein may be distributed architectures (even though shown as a single component). In particular embodiments, the architectural components may be operatively connected in any suitable way.

According to one embodiment of the present disclosure, FIG. 5A is an exemplary sensor device 112, and FIG. 5B is an exemplary RF sensor device 510. Together, and in various embodiments, FIGS. 5A and 5B are exemplary hardware devices including the plurality of sensors, as described herein. In certain embodiments, a plurality of sensors may be included in one all-encompassing device, such as device 112, or various sensors can be standalone sensors, such as the RF sensor device 510. Although two examples of sensor devices are shown, in various embodiments it is possible to include all sensors in a single device.

Referring to FIG. 5A, a plurality of sensors are included in the device 112 shown. The device 112 as shown in the present embodiment includes an X-shape with a circular center but it should be understood from the discussion herein that the device 112, and the RF sensor device 510, may have any shape and are not limited to the shapes as shown on FIG. 5 . According to certain aspects of the present disclosure, the arms protruding from the circular center of the device 112 may house the included sensors. In one embodiment, the arms may be detachable and interchangeable so as to configure the sensor device 112 with an optimal number of each sensor. In other embodiments, the device 112 may include more or less than four arms, or no arms, in order to allow for various configurations of sensors. In the present embodiment, a video sensor 502 may be the circular center of the device 112. According to aspects of the present disclosure, the video sensor 502 may allow for the device 112 to capture and maintain a video stream of a particular field of view, as determined during configuration. In various embodiments, the video sensor 502 may capture 1080p HD resolution video and may be configurable within a 60-120 degree field of view, but also many other fields of view depending on particular device configurations. In one embodiment the video sensor 502 may also be capable of near infrared HD detection. Generally, the video sensor 502 allows for the device 112 to “see” the particular object in order to classify it as a UAV or non-UAV.

In various embodiments, the video sensor 502 may be a PTZ camera, or the like, and the system may dynamically configure the sensor 502 to reorient itself for following an object within an airspace. As will be discussed in greater detail herein, the system may detect the locations of objects in an airspace via sensors such as radar sensors, and furthermore direct the PTZ camera video sensors 502 to those locations for verifying that the detected object is a UAV, and moreover following the UAV through the airspace.

The arms indicated as 504 in the present embodiment may be audio sensors 504, according to aspects of the present disclosure. In certain embodiments, it may be desirable for a particular device to include more than one sensor for reasons such as adding range, accuracy, consistency, or overall better coverage around a particular monitored area when detecting UAVs. In the present embodiment, the device 112 includes two audio sensors 504. In various embodiments, the audio sensors 504 may be capable of detecting stereo audio, which includes audible sonic and ultrasonic frequencies, ranging between 0-96 kHz, but it should be understood from the discussion herein that the audio sensors 504 may be configured to monitor any appropriate frequency range. Generally, the audio sensor 504 allows for the device 112 to “hear” the particular object in order to classify it as a UAV or non-UAV.

Continuing with FIG. 5A, the device 112 as shown in the present embodiment includes at least one Wi-Fi sensor 506. In various embodiments, UAVs may be connected over Wi-Fi to a wireless local area network (WLAN). In one embodiment, including a Wi-Fi sensor 506 on the device 112 may allow for any UAV being controlled and/or being accessed over Wi-Fi to be detected. The process of detecting and analyzing Wi-Fi signals will be further discussed in greater detail in FIG. 13 .

It should be understood from the discussion herein that any type of appropriate sensor that could be useful in identifying, tracking, and managing UAVs may be included in the device 112, and this is indicated at device arm 508 labeled “other”. In various embodiments, examples of these “other” sensors might include high-resolution thermal imaging sensors and radar sensors operating in the ISM-band (Ultra-Wide Band and mmWave-Radar) for detecting UAVs based on heat emissions or particular frequency ranges. In certain embodiments, PTZ-Cameras (EO and Thermal) may be included in order to increase the range of video-based identification and tracking of UAVs. In certain embodiments, device 112 and the attached sensor arms 502, 504, 506, and 508 may include on device computing capabilities and computer memory/storage in order to perform the various processes and functions described herein relating to identifying, tracking, and managing UAVs.

Referring now to FIG. 5B, a single RF sensor device 510 is shown, according to one embodiment of the present disclosure. The RF sensor device 510 may be a standalone sensor, as shown in the present embodiment, or it may be included in the device 112. In one embodiment, the RF sensor may be capable of scanning various industrial, scientific, and medical (ISM) bands, as well as other frequency bands, and detecting signals therein. In certain embodiments, the RF sensor may continuously scan and detect 5 GHz video signals, or signals on any other appropriate carrier frequency and/or frequency range, and further decode the video signals. According to aspects of the present disclosure, some UAVs are equipped with video cameras and may transmit the video signals back to a base station or computing system to be viewed by the UAV operator/controller. In various embodiments, a base station may be a physical remote-control, a smart phone, a video-receiver, or a similar device. In one embodiment, these video signals transmitted from the UAV to a base station may provide information regarding the location of a UAV or the UAV controller, which may aide in the identifying and tracking of the UAV. In certain embodiments, the RF sensor device 510 is configured to detect these signals and extract any information from the signal regarding the presence of a UAV. In some embodiments, the range of an RF sensor such as the RF sensor device 510 may extend to about 500 meters; however, it should be understood from the discussion herein that the range of the RF sensor device 510 may vary according to various configurations. It should be understood that the various sensors described herein are exemplary, and any type of sensor that may be useful in identifying, tracking, and managing UAVs may be included in the present system.

Turning now to FIG. 6 , a flowchart is shown illustrating the exemplary overall system process 600, according to one embodiment of the present disclosure. As will be understood by one having ordinary skill in the art, the steps and processes shown in FIG. 6 (and those of all other flowcharts and figures shown and described herein) may operate concurrently and continuously, are generally asynchronous and independent, and are not necessarily performed in the order shown. Generally, the processes may operate on an electronic computing device (e.g., laptop, remote server, sensor device etc.).

At a high level, and as will be described in further detail herein, FIG. 6 illustrates the process of receiving data from or at sensors, processing the data, determining based on the processed data if a UAV is present, and then determining how to respond to the results. The first step in this process occurs at step 602, where the system is initially configured. Step 602 may allow the system to adjust to and recognize the surrounding environment. In one embodiment, a video sensor included in the present system may need to establish a background before certain background subtraction algorithms can be performed. According to aspects of the present disclosure, at step 602 the video sensor may capture a certain amount of frames in order to establish a background before the system can determine what are static or moving (UAV candidates) objects in a frame. This configuration process of establishing a background before the system begins to identify and track UAVs may be the first step in the process as illustrated; however, a sensor may be configured or reconfigured as necessary throughout the general flow of the system processes. According to aspects of the present disclosure, step 602 may involve configuring the system to adjust for the heading of the video sensor. In certain embodiments, when monitoring and tracking UAVs it may be helpful to have recorded the heading (i.e., yaw, pitch, roll) of the video sensor capturing the data because knowing the heading, as well as the location of the video sensor, may allow for the system to project where the UAV is and will be physically located. In some embodiments, the audio and RF sensors may also be configured at step 602. In various embodiments, it may be beneficial for the audio sensor to detect the frequencies that may be common to the surrounding area. In one embodiment, configuring the RF sensor at step 602 may include establishing a frequency range to monitor. According to various aspects of the present disclosure, the step 602 may include configuring one or more radar sensors to detect objects moving within an airspace. Furthermore, detecting one or more objects in the airspace via a radar sensor may initiate the configuration of other sensors included in the system (e.g., PTZ cameras, RF sensors, etc.). In particular embodiments, the system configuration step 602 may include the physical installation and deployment of the device 112, various sensors, and other hardware on various installation locations 110. According to various aspects of the present disclosure, the step 602 is intended to allow for the system and included sensors to prepare for functional operation.

Continuing with step 602, configuration of the system may include establishing a connection between all sensors included in the UAVTMS 102, devices 112, installation locations 110, networks 108, third party data sources 120, etc. In various embodiments, exemplary operation of the system may rely on the ability of all elements of the system to communicate with each other.

Once the system is configured, each individual sensor may begin to collect data and perform operations and processes on the collected data as necessary. As shown in the present embodiment, the video data analysis process 700 (FIG. 7 ), audio data analysis process 1100 (FIG. 11 ), RF data analysis process 1200 (FIG. 12 ), Wi-Fi analysis process 1300 (FIG. 13 ), and other additional sensor acquisition and analysis processes 604 may begin to operate once the configuration of the system at step 602 is complete. As will be understood by one having ordinary skill in the art, these processes may operate autonomously, asynchronously, and independently of each other. In particular embodiments, these processes may or may not all operate at the same time, and in some embodiments some processes might not operate at all depending on the sensors included in the particular device 112. According to various aspects of the present disclosure, each process mentioned immediately above may begin once any prerequisite configurations have been completed at step 602. For example, the Wi-Fi data analysis process 1300 may begin its exemplary process while the video data analysis process 700 is still being configured. In one embodiment, these processes may operate locally and within the circuitry of each individual sensor. In other embodiments, the data from each sensor may be directed to a separate computing element, such as the management module 104, for further processing. In general, each process mentioned above collects data and analyzes the data in order to determine if a UAV is present in its respective surrounding area. Briefly mentioned above and in various embodiments, step 604 is an optional process that may allow additional sensors to operate and be supported on the device 112. For example, if a sonar sensor (or additional radar sensors/PTZ cameras) was added to the device 112, step 604 might incorporate the additional processes required to operate the sonar sensor in addition to the present system configuration. In various embodiments, the sensor processes may output a confidence level. This confidence level may be a number or value that is an indication of how likely it is that a detected object is a UAV.

At step 606, the confidence levels outputted from each sensor data analysis process may be aggregated. In one embodiment, the aggregation of confidence levels may include the use of mathematical processes to determine if an identified object is a UAV or not. In various embodiments, a scenario may arise where the confidence level based on the data from a Wi-Fi sensor may indicate a near 100% UAV presence. In the same scenario, the confidence level based on the data from an audio sensor may indicate only a near 60% UAV presence. The aggregation step 606 may be configured to take the confidence levels from each sensor and combine them in order to make a decision regarding the presence of a UAV. In certain embodiments, the aggregation of confidence levels step 606 may be optional if a particular sensor detects a near 100% confidence level and directly forwards the information to the notifications module 410.

Proceeding to step 608, the system may evaluate if a UAV was identified based on the confidence levels aggregated at step 606. In one embodiment, evaluating if a UAV was identified based on a collection of one or more confidence levels may include comparing the one or more confidence levels to a predetermined threshold of confidence levels and/or rules regarding UAV likelihoods. In certain embodiments, step 608 may be configured to automatically determine that the object detected is a UAV based on a near 100% confidence level indication from Wi-Fi data, or data from another sensor. In other embodiments, step 608 may be configured to process a combination or average of all confidence levels, and then compare the results to a predetermined threshold. For example, if the threshold for an object to be considered a UAV is 80%, and the average of all confidence levels is 75%, the object may be determined non-UAV regardless if some of the confidence levels were above the 80% mark. The output from step 608 is typically a boolean, indicating a yes or no decision if a UAV has been identified. If it is determined that a UAV is identified, the process may continue to step 610 where the information regarding the UAV is stored for future use. According to various aspects of the present disclosure, step 610 may involve indicating within the system that if future detected signals indicate substantially similar characteristics to the signals previously determined to be originating from a UAV, then those signals should be assumed to be from a UAV.

Continuing with FIG. 6 , at step 610 the information regarding a detected UAV is stored in a database such as the Drone/UAV DNA database 412 or system management database 414. In various embodiments, storing the information regarding the detected UAV includes storing any videos of the UAV, noise patterns, controlling frequencies, Wi-Fi network specifications, transmitted data such as video captures and GPS locations, radar readings/3D coordinates, timers/counters for time spent verifying a UAV, etc., that may be used in the future for detecting other UAVs, or managing and recognizing previously detected UAVs.

At step 612, an action regarding the UAV may be made based on a predetermined rule set. This decision could include a wide variety of actions, such as ignore the UAV because it is known to be trusted, or attempt to locate the controller of the UAV because it is identified as a threat. In one embodiment, these rules and instructions are stored in the database 106 included in the UAVTMS 102. In some embodiments, the predetermined rules may be categorized by confidence level thresholds or particular types of sensors, such as a Wi-Fi sensor, that may effectively indicate a UAV presence. After a decision is made regarding how to respond to the identified UAV at step 612, or if a UAV was not identified at step 608, the system may determine if it should continue monitoring the surroundings for UAVs at step 614. If the system is to continue monitoring, the process may proceed to the beginning of the flow where it will continue to intake sensor data. If at step 614 it is determined that the system should no longer continue monitoring, then the process may be terminated. In most scenarios, the system will monitor continuously while operational. If it were decided to discontinue monitoring at step 614, the system may need to reconfigure the sensors and devices to transmit data to the management module 104.

FIG. 7 is a flowchart illustrating the exemplary video data analysis process 700, according to one embodiment of the present disclosure. At step 702, an individual video frame is received from the video data stream as recorded from the video sensor. In a particular embodiment, the video frame received at step 702 may be an individual frame not included in a stream, but is rather a targeted picture, or the like, taken on command, at a predetermined time interval, in response to the system detecting an object at a particular location, etc. In one embodiment, the video data may be captured via one or more PTZ cameras, where these cameras may capture 1080p HD formatted media, or another appropriate video/photo format. In certain embodiments, the video stream may be transmitted to the central system of the UAVTMS 102 over a network 108 for processing, or the video stream may be processed locally.

Proceeding to step 704, background subtraction algorithms may be performed on the received video frame in order to detect changes between the current video frame and a background frame. In general, video sensors operate by capturing multiple frames per second. Each frame from the video data stream may not seem to be significantly different from the previous frame; however, if the two frames are closely analyzed then differences between the frames can be found. As will be understood and appreciated by those skilled in the art, background subtraction is a computing process whereby given a frame that represents a relatively constant background, motion or new elements in subsequent frames can be detected by comparing the pixels and/or pixel color values of the declared background frame to new frames. In various embodiments, each frame included in the video data stream is compared to the background frame. In one embodiment, frames included in the video data stream are periodically compared to the background frame, such as every fifth frame or another appropriate number of frames. After comparing the frames, an area in the frame where the pixel values have changed is an indication of motion or a delta between the frames. Generally, a typical background subtraction output may include only black and white pixels. In these outputs, a black pixel is swapped with the original pixels where there was little or no delta detected, and a white pixel is swapped with the original pixels where a delta between the pixel values were detected. For example, consider a video frame of a clear sky compared to a video frame of a clear sky with a bird in the frame. According to the principles of background subtraction, subtracting corresponding pixel color values between the two frames may result in a difference at the location where the bird is present, and the output may be a background of black pixels with a cluster of white pixels representing the bird. In particular embodiments, the background frame may be established in the system configuration step 602 previously described in FIG. 6 . In one embodiment, establishing a background may involve capturing only the first frame when a video sensor is configured. In other embodiments, a background is established once there is minimal or no change between a group of subsequent frames or for a certain amount of time. In certain embodiments, a background is continuously updated once established, and may adjust for natural changes in the environment (e.g., cloud formations, natural lighting due to time of day, etc.).

At step 706, the output of the background subtraction algorithm is analyzed to identify if regions of interest (ROIs) are present in the frame. In various embodiments, a region of interest is a cluster of pixels in a video frame that may indicate a potential UAV and should be further analyzed. In one embodiment, if movement was detected during the background subtraction process at step 704, that area of change may be identified as a region of interest. In certain embodiments, if a cluster of pixels indicating movement is identified within a frame, the system may recognize a rectangular portion of the frame that fully encompasses the cluster of pixels as a region of interest. As shown in FIG. 8 , the regions of interest 802A-802C encompass certain objects within a frame that have been detected as moving. According to various aspects of the present disclosure, when a ROI is being processed or analyzed, the location of the ROI within the video frame may be located within the frame by referencing the top left corner pixel location and bottom right corner pixel location of the rectangular portion of the ROI in the video frame as mentioned above.

In some embodiments, during the video data analysis process, an entire video frame may be processed between steps; however, the top left and bottom right corners of the rectangular portion of the video frame may indicate the boundary of the ROI and limit the processing to just that region of pixels. If no ROIs are detected in the frame, then the process may jump to step 720 to determine if there are more frames to be analyzed. In one embodiment, if no ROIs are detected in the frames then the video frame received at step 702 may be substantially similar to the background frame. If it is determined at step 706 that ROIs are present in the frame, the video data is forwarded to the ROI Tracking process 1400.

As will be later described in FIG. 14 , the ROI tracking process 1400 involves comparing ROIs from the frame received at step 702 to ROIs to previous frames stored in a database within the UAVTMS 102. In one embodiment, comparing various aspects of ROIs such as size and position within the frame may allow for the system to track ROIs and predict where they will be located over time. In certain embodiments, ROIs may be rejected as possible UAVs during the ROI Tracking process 1400 based on the results from the size and position comparisons mentioned above. According to aspects of the present disclosure, the output from the ROI Tracking process 1400 is one or more ROIs that have either been tracked or rejected. These ROIs further are directed to step 708 where it is determined if the ROI is tracked or rejected.

At step 708, the system determines if an ROI has been tracked. As briefly mentioned above, if an ROI has not been tracked then it has been rejected as a possible UAV candidate during the ROI tracking process 1400. In various embodiments, if an ROI has been rejected or not tracked, the process continues to step 720 where the system determines if there are more frames to analyze. If an ROI has been tracked, then the system proceeds to step 710 where it is determined if the one or more ROIs are in an attention region.

In one embodiment, step 710 determines if the one or more ROIs that were previously tracked in the ROI tracking process 1400 are in an attention region. According to various aspects of the present disclosure, an attention region is an area within a frame where heightened attention should be focused due to a recently UAV-classified ROI being present within that area. In various embodiments, the purpose of an attention region is to prevent an ROI that may be a UAV from being falsely rejected during the scene learning process 900 operating within the system. Generally, an attention region is a circular region encompassing a certain area (proportional to the size of the ROI) of pixels within the frame where a recently classified UAV may be. In various embodiments, the attention region may be of any shape appropriate and should not be limited to being circular. A visual representation of a region of interest and attention region can be seen in FIG. 8 .

Continuing with FIG. 7 , at step 710 if the one or more ROIs are included in an attention region, the process may skip to the object classification process 1000. In this scenario, the process skips to the object classification process 1000 because the region of interest is most likely a UAV and may be labeled as a non-UAV during the scene learning process 900 due to its location within an attention region. In various embodiments, if the one or more regions of interest are not in an attention region, the process proceeds to the scene learning process 900. The scene learning process 900 will be discussed in greater detail in FIG. 9 , but it should be understood that the scene learning process 900 generally compares one or more regions of interest to various other know regions of interest in order to determine if the region of interest is new to a particular scene or if it is a reoccurring region of interest. In various embodiments, the output from the scene learning process 900 may be one or more regions of interest that are indicated as either being recognized within the expected scene, or not.

At step 712, if the one or more regions of interest are not indicated as being recognized by the scene learning process 900 then the process proceeds to the object classification process 1000 in order to determine and classify what the regions of interest may be, and more particularly if they are UAVs. If at step 712 it is determined that the one or more regions of interest from the scene learning process 900 were recognized within the scene, the process proceeds to step 714, where the one or more regions of interest are stored for a finite period. In one embodiment, storing the one or more regions of interest for a finite period of time allows for the central system of the UAVTMS 102 to be able to compare the recently stored ROIs to newly detected ROIs.

As briefly mentioned above, ROIs that were indicated as not being recognized in the particular scene are forwarded to the object classification process 1000. Generally, the object classification process 1000 compares various aspects of the one or more regions of interest to corresponding aspects of known UAVs and non-UAVs. In various embodiments, the output from the object classification process 1000 is one or more regions of interest that have been classified as either UAV or non-UAV.

At step 716, the outcome from the object classification process 1000 is evaluated. If the one or more regions of interest were determined to be non-UAV, then the one or more regions of interest may be stored for a finite period of time within a database, such as the database 106 of the central system of the UAVTMS 102. If the one or more regions of interest were classified as UAVs, then attention regions are added to the frames in the locations of the corresponding regions of interest. In various embodiments, attention regions are added to frames as a result of recently identified and classified UAVs. At step 718, the attention regions added to the frame correspond to the one or more regions of interest and may prevent the one or more regions of interest from being disqualified as UAVs during the scene learning process 900.

In one embodiment, at step 720 the process determines if there are additional frames to be analyzed. In various embodiments, if there are additional frames to be analyzed then the process may proceed to 702 in order to receive an additional video frame. In certain embodiments, if there are no additional frames to analyze then the process may terminate.

FIG. 8 is a representative frame 800 from a video stream at a particular video sensor, according to one embodiment of the present disclosure. In the present embodiment, a scene is shown including three identified regions of interest 802A-802C as well as one attention region 804. In one embodiment, the three regions of interest 802A-802C may have been identified due to movement around these objects after the background subtraction algorithms were performed at step 704. The left most region of interest is a set of trees 802A, the middle region of interest is a bird 802B, and the right most region of interest is a UAV 802C. In various embodiments and as will be discussed later in the detailed description of FIG. 10 , the region of interest identifying the set of trees 802A may be analyzed and quickly dismissed as a non-UAV. Trees generally remain stationary over time; however, external factors such as wind may cause trees to bend and move slightly. This movement may trigger trees to be flagged as regions of interest, but as will be discussed further in the scene learning process 900, objects such as trees will most likely be quickly dismissed as non-UAVs. The center region of interest, the bird 802B, most likely was recognized by a video sensor and flagged as a region of interest once it flew into the video sensor's field of view. According to embodiments of the present disclosure, the bird 802B will most likely be dismissed as a non-UAV, but the bird 802B may require classification as compared to the trees 802A. In many embodiments, a bird is not included in the scene-model. In some embodiments, a video sensor may not be able to distinguish the difference between a bird and a UAV and will assign the region of interest a higher confidence level. In other embodiments, the bird may be assigned a low confidence level because the bird is common to the area and has been recognized and classified as non-UAV many times before. In particular embodiments, the objet classification process is configured to automatically negate the possibility of the bird 802B being classified as a UAV without assigning a confidence level.

Continuing with FIG. 8 , a region of interest including a UAV 802C is present in the representative frame 800. In one embodiment, the region of interest including the UAV 802C may be initially classified as a UAV, as described later in the discussion of FIG. 10 . In various embodiments, when a region of interest is classified as a UAV, an attention region 804 is established around the region of interest 802C. In the present embodiment, an attention region 804, indicated as a circle around the region of interest including the UAV 802C, has been added to the representative frame 800. As mentioned previously in FIG. 7 , an attention region 804 is a zone surrounding a recently classified UAV region of interest, such as the region of interest including the UAV 802C, intended to prevent the region of interest from potentially being disqualified as a non-UAV. In various embodiments, the attention region 804 is proportional to the particular region of interest it corresponds to, such as the region of interest 802C, and may represent an area within the representative frame 800 where the region of interest 802C may reasonably be located after a certain amount of time. For example, in one scenario, the region of interest including a UAV 802C may be identified in one location and be attributed an attention region 804, but then later the region of interest 802C may enter the region of interest including the trees 802A. In that scenario, the attention region 804 may prevent the scene learning process 900 from associating the region of interest including the UAV 802C as being included in the region of interest of trees 802A. If the attention region 804 was not present, the region of interest including the UAV 802C may be mistaken for the trees 802A, which may result in the inability to continue tracking the region of interest including the UAV 802C.

Still referring to FIG. 8 , present in the representative frame 800 but not identified as a region of interest is a house 806. The house 806 is not labeled as a region of interest because it is a stationary object and would not be indicated as having moved in a background subtraction algorithm at step 704. According to various aspects of the present disclosure, the house 806 may be included as a part of the background.

Referring now to FIG. 9 , a flowchart illustrating the scene learning process 900 is shown, according to one embodiment of the present disclosure. According to aspects of the present disclosure, the input to the scene learning process 900 may be one or more ROIs not included in attention regions, received from the process described at step 710 of FIG. 7 . In general, the scene learning process 900 receives one or more regions of interest not included in attention regions and compares the one or more regions of interest to various aspects of regions of interest that have been previously identified by the system.

In one embodiment, the scene learning process 900 begins at step 902 by analyzing one or more regions of interest. As briefly mentioned above, these regions of interest were determined to not be included in attention regions at step 710.

In various embodiments, step 904 compares aspects and characteristics of the one or more regions of interest to corresponding aspects and characteristics of stored regions of interest. In various embodiments, the aspects and characteristics that may be compared include position within the video frame, size of the region of interest, motion characteristics, content of the one or more regions of interest, and others. In particular embodiments, the results from these comparisons may be evaluated based on predetermined thresholds, or the comparisons may need to be complete matches. In an example scenario, if a region of interest is compared to a recently stored region of interest and it is determined that both regions of interest are located in similar positions within their respective video frames, the sizes of both regions of interest are generally the same but one may have increased or decreased slightly, both regions of interest have been tracked moving similar amounts and directions between frames, and if both regions of interest have similar content, it may be determined that the particular region of interest received is recognized by the scene learning process 900.

According to various aspects of the present disclosure, step 906 determines if the one or more regions of interest received at step 902 match any or all of the corresponding aspects and characteristics compared during step 904. If at step 906 the results from the comparison at step 904 match or are within a certain threshold, or if the comparisons match completely, the process may proceed to step 908 where the one or more regions of interest are indicated as being included within the scene. In various embodiments, being included within the scene may mean the particular one or more regions of interest may be recognized or remembered by the system. Otherwise, the one or more regions of interest may not be identified as being included within the scene at step 908 and instead the process may proceed to step 910 where it is determined if there are more regions of interest to compare.

At step 908, the one or more regions of interest that were determined to be matches to previously detected regions of interest within the particular scene and based on a predetermined threshold are indicated as being included within the scene and may be further recognizable by the scene learning process 900. In various embodiments, being recognized by the scene learning process 900 may result in one or more regions of interest not being processed by the object classification process 1000. In one embodiment, once the one or more regions of interest are indicated as being included in the particular scene, the process may proceed to step 910 where it is determined if there are more regions of interest to analyze. If there are more regions of interest to analyze, the process may proceed to step 902, otherwise the process may terminate.

FIG. 10 is a flowchart illustrating the object classification process 1000, according to one embodiment of the present disclosure. According to aspects of the present disclosure, the object classification process 1000 may be initiated when an unrecognized region of interest is identified by the video sensor (e.g., PTZ camera). In various embodiments the process may begin by receiving one or more unrecognized regions of interest at step 1002. The one or more regions of interest received at step 1002 may have been previously analyzed in the scene learning process 900 described above in FIG. 9 , and the system may have determined that the one or more regions of interest do not correspond with any previously classified or stored regions of interest. Once the one or more regions of interest are received at step 1002, the process may proceed to steps 1004A, 1004B, 1004C, and 1004D, where various aspects of the one or more regions of interest are analyzed. In general, the steps 1004A, 1004B, 1004C, and 1004D involve extracting meta-information from the one or more regions of interest and each process may execute simultaneously but also independently of each other.

In one embodiment, step 1004A involves extracting red, green, and blue (RGB) color values from the pixels within the one or more ROI locations. In various embodiments the ROI location may be determined from the top left and bottom right locations of the rectangular portion of the video frame forming the ROI boundary, as discussed above in FIG. 7 . In certain embodiments, extracting RGB color values from the pixels included in the one or more ROIs may help determine if the ROI should be classified as UAV or non-UAV. In various embodiments, UAVs may typically be manufactured out of similar materials, painted with similar colors, or have similar shapes. In one embodiment, a recognizable pattern of material, paint colors, or shapes across various UAVs may allow for the system to classify a region of interest as a UAV based on the color and color gradient similarities.

In other embodiments, step 1004B may involve extracting the background subtraction data from the one or more regions of interest. In various embodiments, the background subtraction data may be an indication of the shape of the moving object (as compared to the rigid shape of the rectangular ROI) and how a region of interest is moving across a particular frame. In one embodiment, the background subtraction data may indicate a large delta between frames, which may indicate that the region of interest is moving relatively fast or that the region of interest may be relatively close. In other embodiments, the background subtraction data may indicate a small delta between frames, which may indicate that the region of interest is moving slowly or possibly that the region of interest is far away. This background subtraction meta-data, in various embodiments, may allow for the object classification process 1000 to determine if a region of interest is behaving in a manner which would be similar to that of a UAV and if the object within the region of interest has a similar shape to that of a UAV.

Continuing with FIG. 10 , step 1004C involves extracting RGB color values from the pixels within the one or more ROI locations from previous frames. In one embodiment, extracting RGB colors from ROIs of previous frames may allow for the object classification process 1000 to use temporal color information to compare previously classified ROIs to currently unclassified ROIs in an attempt to make a similar classification decision. In various embodiments, step 1004D may allow for other ROI meta-information to be extracted from the current one or more regions of interest, as well as regions of interest from other frames.

In some embodiments, the video sensor may capture frames of different sizes or dimensions than other video sensors. In order to ensure consistency during the object classification process 1000, the frames may be scaled to a uniform size at step 1006. Step 1006 is an optional step and need not always be executed. If the video frame does not need to be scaled, the process may continue to step 1008, where the one or more regions of interest are compared to examples of known UAVs and non-UAVs stored in databases 412 and 414. In one embodiment, the machine learning technique referred to as deep learning may be used at step 1008 to make comparisons between the one or more regions of interest and the examples of known UAVs and non-UAVs. According to various aspects of the present disclosure, deep learning may allow for conclusions to be drawn from making relationships between many data points (sensor data). Deep learning may allow for the system to not only better classify the one or more regions of interest, but also improve the scope and efficiency of the current deep learning algorithms over time. In general, the system may become more sophisticated as the number of classified regions of interest increases because there will be more classified regions of interest to make comparisons and relationships to.

In one embodiment, the system proceeds to step 1010, where the UAV and non-UAV confidence levels may be determined for the one or more regions of interest. In various embodiments, if the comparison results from step 1008 above indicate that previously UAV-classified regions of interest are substantially similar to the one or more regions of interest currently being analyzed then the UAV confidence level for the one or more regions of interest may be relatively high. In other embodiments, the opposite of the above scenario may be true if the comparison results from the step 1008 above indicate that previously non-UAV classified regions of interest are substantially similar to the one or more regions of interest currently being analyzed.

In various embodiments, the UAV and non-UAV confidence levels determined at step 1010 are compared at step 1012. According to aspects of the present disclosure, if the UAV confidence level is greater than the non-UAV confidence level then the process may proceed to step 1014 where the one or more regions of interest are classified as UAV. If it is determined that the UAV confidence level is not greater than the non-UAV confidence level, then the process may to proceed to step 1016 where the one or more regions of interest are classified as non-UAV. In various embodiments, once one or more regions of interest are classified as a UAV or non-UAV the one or more regions of interest may be stored in the databases 412 and 414 for future processes.

FIG. 11 is a flowchart illustrating the audio data analysis process 1100, according to one embodiment of the present disclosure. In various embodiments, the exemplary audio data analysis process 1100 shows how an audio signal is analyzed and processed in order to determine if the signal was produced by a UAV. At step 1102, the process 1100 begins when an audio sensor receives or detects an audio signal, or when the central system of the UAVTMS 102 receives an audio data from an audio sensor. According to aspects of the present disclosure, this signal may be an analog or digital signal. In some scenarios, if an environment is known to produce certain frequency patterns, then it is possible to detect frequencies that are not common. In accordance with aspects of the present disclosure, UAVs may emit frequencies that are easily recognizable. In one embodiment, the audio signal may be emitted from the motors, propeller blades, or other components of a UAV.

Proceeding to step 1104, the audio signal may be converted from the time domain (as received) to the frequency domain using a Fast Fourier Transform (FFT), or another signal processing method. According to aspects of the present disclosure, an FFT may allow for a signal such as an audio signal to be represented as a combination of frequencies. Generally, an audio signal may include many frequencies but all that is heard to the human ear is one continuous noise. An FFT may allow for each individual frequency included in the signal to be represented along a frequency axis. In certain embodiments, converting the audio signal to the frequency domain may involve converting the signal into 8096 different values, each covering some portion of the audio frequencies from 0 Hz to 192 kHz. According to various aspects of the present disclosure, the signal may be converted into more or less values as necessary, and also the values may cover frequencies that exceed 192 kHz.

In various embodiments, once the audio signal is converted to the frequency domain at step 1104, the process may proceed to step 1106 where the sound data is updated. According to aspects of the present disclosure, updating the sound data may include storing the detected frequencies in a database such as the database 106 of the UAVTMS 102. In particular embodiments, updating the sound data may include updating a log of information within the UAVTMS 102 regarding particular frequencies and how often they are detected by the audio sensor. Once the sound data is updated at step 1106, the process may proceed to step 1108, where the frequency to noise volume ratio may be compared to a predefined threshold. In certain embodiments, step 1108 may involve evaluating all of the frequencies detected in the signal. In some embodiments, while evaluating all of the frequencies present in the signal, if a frequency sample with very low amplitude, such as noise, is evaluated, the system may determine that the amplitude corresponding to the particular frequency is below a certain threshold and discard the sample. In certain embodiments, a frequency sample with high amplitude may be disregarded, such as a sampling artifact. In various embodiments, step 1108 may be intended to filter out frequency samples that are most likely not indicative of a UAV.

In the above scenarios, if a frequency sample with a particular amplitude is disregarded at step 1108 for not being within a certain threshold, the process may proceed to step 1110. In certain embodiments, at step 1110 the system may check if there are more frequencies from the converted signal to analyze and compare. If at step 1110 it is decided that there are more frequencies to compare then the process may jump back to the beginning of step 1108 in order to compare another frequency from the updated sound data.

Continuing with FIG. 11 , and according to one embodiment, at step 1108 if it is determined that particular frequency to noise volume ratios are within a certain threshold, the process may proceed to step 1112, where the frequency may be compared to other stored and known UAV frequencies. For example, at step 1112 the system may be configured to compare the current frequencies to frequencies know to be emitted by specific UAVs (e.g., DJI Phantom 2 at 18 kHz, etc.). In other embodiments, the system may be configured at step 1112 to analyze a frequency and determine if a signal is encoded into the frequency. In some embodiments, detecting a signal encoded into a frequency may be an indication of a UAV that may or may not have been previously encountered. According to various aspect of the present disclosure, the comparisons and evaluations made at step 1112 may result in a confidence level being determined regarding a signal being an indication of a UAV or not. If at step 1112 it is determined that a particular frequency does not match with a known UAV frequency or frequency patter then the process may proceed to step 1110 as briefly described above, otherwise the system may proceed to step 1114.

In various embodiments, step 1114 includes taking predetermined action regarding a recently detected UAV. In one embodiment, a recently detected audio signal may have included frequencies that are strong indications of a UAV and as a result, the system may be configured to respond accordingly. At step 1114, it may be decided to trigger an alarm regarding the potential UAV to be sent to a user 118 monitoring the system. In other embodiments, it may be decided at step 1114 to attempt to locate the potential UAV or the UAV controller in order to and take forceful action such as jamming any UAV capabilities or possibly targeting the UAV with a weapon (e.g., laser, missile, various projectiles, etc.). In particular embodiments, the predetermined action may simply include assigning a confidence level corresponding to the particular frequency or audio signal for use in subsequent decision making or analysis. Regardless of the outcome at step 1114, the process may proceed to step 1116 where the data from previous steps is transmitted to a database or server, such as the database 106 of the UAVTMS 102. In other embodiments, the data from previous steps may be stored locally.

Still referring to FIG. 11 , once the data from step 1116 is transmitted to a database or server such as the databases 106, 412, and 414, the process may proceed to step 1110. Briefly mentioned above, at step 1110 it may be determined if there are more frequencies from the converted signal to compare. In one embodiment, if there are more frequencies to compare then the process may jump back to the beginning of step 1108 in order to compare another frequency from the updated sound data. In various embodiments, at step 1110 if it is determined that there are no more frequencies from the converted signal to compare then the process may proceed to step 1118.

In certain embodiments, at step 1118 the system may determine if the exemplary audio data analysis process 1100 should continue to receive audio signals or if it should terminate. According to various aspects of the present disclosure, if the system determines that it should continue to receive audio signals then the process may jump back to step 1102. In most scenarios, the system will continue to receive audio signals. If it was decided to discontinue receiving audio signals at step 1118, the exemplary audio data analysis process 1100 may need to reconfigure the audio sensor if the process were to later resume.

FIG. 12 is a flowchart illustrating the radio frequency analysis process 1200, according to one embodiment of the present disclosure. UAVs are commonly controlled from remote base stations that emit flight controls to the UAVs over radio frequencies. In various embodiments, UAVs may also transmit data (e.g., live video captures, battery status, GPS location, etc.) back to the remote base stations. A UAV controller may transmit RF signals to the UAV over any frequency included in the radio frequency spectrum (3 kHz-300 GHz); however, RF communications are typically restricted by government regulations to certain sub-ranges within the spectrum. Traditional radio transmitters and receivers are designed to operate under the frequency limitations as well as modulation and channel coding capabilities as defined by their hardware configurations. However, a software defined radio (SDR) is a device that includes hardware components that are reconfigurable by software, allowing the SDR to monitor a dynamic range of frequencies. A SDR generally operates similarly to a traditional radio, but the reconfigurable hardware in a SDR allows for it to monitor a larger range of frequencies without requiring additional hardware. In one embodiment, the system is configured with at least one SDR in order to monitor an environment for UAVs being controlled by signals communicated over various frequencies in the radio frequency spectrum.

In various embodiments, the exemplary RF data analysis process 1200 begins at step 1202 when the RF sensor receiver is tuned to a particular frequency. In one embodiment, the RF sensor includes a RF signal receiver that is configurable to receive data from RF signals over certain frequencies. According to aspects of the present disclosure, tuning the receiver at step 1202 may involve programing the SDR to monitor particular frequencies. In various embodiments, step 1202 may involve configuring the RF receiver to be tuned into a particular frequency for a predetermined amount of time, and then re-tuning the RF receiver to a different frequency after that predetermined amount of time. In certain embodiments, this process is known as an “RF Sweep”. Once the RF sensor is tuned at step 1202, the RF receiver may detect a signal being carried over the particular tuned frequency, after which the process proceeds to step 1204.

According to various embodiments, the RF signal data is received at step 1204. In one embodiment, receiving the RF signal data includes detecting various signal characteristics (e.g., signal power, energy, gain, etc.) that would not typically be present on an idle carrier frequency. At step 1204, receiving RF signal data including the various signal characteristics mentioned immediately above is an initial indication that a UAV being controlled by RF signal may be in the vicinity; however, the following steps allow for the system to further determine the content of the received RF signal.

Indicated by the dashed box, steps 1206 and 1208 are optional in the exemplary RF data analysis process 1200. In one embodiment, step 1206 includes filtering the received RF signal data, and step 1208 includes determining if the energy from the filtered RF signal data exceeds a predefined energy level. In various embodiments, filtering the RF signal data at step 1206 may involve filtering out certain unwanted components from the RF signal data. According to various aspects of the present disclosure and as will be understood and appreciated by one skilled in the art, certain filters such as low pass filters, band pass filters, high pass filters, etc., may allow for certain unwanted frequencies (such as noise or sampling artifacts) to be removed from the RF signal data. Removing particular unwanted frequencies from the RF signal data may allow for only a desired portion of the RF signal data to be analyzed which may result in more accurate predictions regarding UAV presence.

Once the RF signal data is filtered at step 1206, the system may determine if the signal energy is above a predefined threshold at step 1208. In various embodiments, at step 1208 the circuitry within the RF sensor may be physically processing the received and filtered RF signal data, and if the energy levels within the circuitry are not above a predefined threshold then the RF signal data may be rejected as a UAV identifiable signal. Rejecting the RF signal data based on signal energy below a predefined threshold may result in the process proceeding to step 1218 in order to determine if the system should continue to receive more RF signals. At step 1208, if it is determined that the energy from the RF signal data exceeds a certain predefined threshold then the process may proceed to step 1210.

In one embodiment, step 1210 involves filtering the RF signal data using a Finite Impulse Response (FIR) Filter. Similarly to step 1206, step 1210 filters the RF signal data and may remove particular frequencies from the sampled RF signal data based on the particular filter design. In some embodiments, when steps 1206 and 1210 both occur in the exemplary RF data analysis process 1200, the filtering processes of steps 1206 and 1210 may operate in parallel and simultaneously filter the same RF signal data.

Step 1212 of the exemplary RF data analysis process 1200 includes the process of decoding the RF signal data. In one embodiment, decoding the RF signal data allows for the message encoded into the RF signal to be extracted and further understood. In signal processing, the process of encoding a message or information into an electromagnetic wave of a certain frequency is called modulation. In certain embodiments, once this signal data is received such as in step 1204, the message in the signal cannot be understood until it is demodulated, or decoded. This process happens at step 1212 in the present embodiment. In various embodiments, the signal decoded at step 1212 may include instructions regarding future UAV behaviors, video captures from the UAV, UAV battery levels, etc. Decoding the RF signal data at step 1212 may allow for a controller of the system, such as a user 118, to extract and make use of the information detected in the particular RF signal.

At step 1214, the system may determine if the filtered and decoded RF signal data is recognized by the system. In one embodiment, the filtered and decoded data may be a collection of frequencies and amplitudes represented along a frequency axis. According to various aspects of the present disclosure, this collection of frequencies may be arranged in a particular pattern that may indicate a UAV presence. In some embodiments, the UAVTMS 102 may have RF frequency patterns known to indicate the controlling of a UAV from a remote base station stored in databases such as databases 412 and 414 including calibration data or other data. The system may use these stored frequency patterns to determine if the filtered and decoded RF signal data is recognized or not. If at step 1214 it is determined that the frequency pattern is unrecognized, then the exemplary RF data analysis process 1200 may continue to step 1218 where it is determined if the system should continue to receive RF signals.

In one embodiment, if the frequency pattern is recognized at step 1214, the process may proceed to step 1216 where a predetermined rule set including information regarding how to respond to the recognized frequency pattern may determine how to best react to the recognized RF signal data. In an example scenario, the monitored environment may be a residential home and a recognized frequency pattern may be detected. The system may then decide to alert a user, which may be the owner of the house in this scenario, to decide how to handle the situation. The user may then decide simply to close the blinds in their home or potentially contact an authority. In certain embodiments, the predetermined rule set may determine that a high confidence level should be assigned to the particular RF signal data being received if the RF signal data is recognized.

Once a decision is made based on a predetermined ruleset at step 1216, the exemplary process 1200 may proceed to step 1218 where the system determines if it should continue receiving RF signals. In one embodiment, if the system determines that it should continue to receive RF signals, the process may jump to step 1202 in order to tune or re-tune the RF receiver. In other embodiments, if the system determines that it should not continue to receive RF signals then the process may terminate.

FIG. 13 is a flowchart illustrating the exemplary Wi-Fi data analysis process 1300, according to one aspect of the present disclosure. In various embodiments, UAVs and other various remote controlled devices may be connected over Wi-Fi to a wireless local area network (WLAN) or establish their own local Wi-Fi access points. Similar to connecting a mobile device to the wireless internet at a local coffee shop, the process of connecting a UAV to a WLAN over Wi-Fi involves sharing some initial information. Typically, and in various embodiments, this information may include network names, passwords, device identifiers, and other relevant credentials. In one embodiment, a common credential to share in order to gain network address is a MAC address. A MAC address is a unique identifier assigned to devices or other networks interfaces. In certain embodiments, when a device is connected to a WLAN, the MAC address of that device may be communicated to the network source and included in any communications to and from the device. According to aspects of the present disclosure, a UAV may be manufactured to include a unique MAC address, and a portion of that MAC address may identify the manufacturer. In some embodiments, if a MAC address is readable from communications being transmitted and received from a UAV, it may be possible to determine the UAV manufacturer which may provide insight regarding how to take action against the UAV if necessary.

In addition to MAC addresses, most Wi-Fi signals include a service set identification (SSID) along with any other information being transmitted or received. In various embodiments, SSID's may be thought of as a “network name” as they are often used as network identifiers when transmitting information. In various embodiments, once a device is connected to a network, the SSID of that network will be included in any communication transmitted or received between the device and network connection source. In one embodiment, if a SSID is readable from communications being transmitted over a network, it is possible to determine if that network is trusted based on if the network SSID is recognized.

In one embodiment, when communication signals such as Wi-Fi signals reach a sensor they may be received with a particular strength. This strength may be converted, through the internal circuitry of the receiver, into a relative received signal strength indicator (RSSI). In certain embodiments, a high RSSI may indicate a strong signal and a low RSSI may indicate a weak signal. In various embodiments, this RSSI may help determine how strong a network is and potentially how close a UAV is if that UAV were being controlled over Wi-Fi. In certain embodiments, a general Wi-Fi sensor may include the functionality required to detect Wi-Fi signals and the information communicated over Wi-Fi signals as described above.

Now beginning at step 1302 in the present embodiment, the Wi-Fi sensor is tuned to a particular channel. Generally, Wi-Fi signals are transmitted over certain channels defined by certain frequencies. Typically, these channels are classified by numbers (i.e. 1-14) and are defined by frequencies increasing on a scale of 5 MHz per channel. For example, channel one operates on 2412 MHz, channel 2 operates on 2417 MHz, channel 3 operates on 2422 MHz, and so on. In one embodiment, at step 1302 the Wi-Fi sensor is tuned and configured to monitor these channels in an effort to detect W-Fi data transfers. In various embodiments, the Wi-Fi sensor may only be tuned to one channel at a time. In particular embodiments, the Wi-Fi sensor may be tuned to various channels at a time. In certain embodiments, being tuned to a certain frequency channel may allow for the Wi-Fi sensor to monitor each channel for a certain amount of time in order to detect a transfer of data packets between a UAV and a Wi-Fi access point. In one embodiment, the Wi-Fi sensor does not need to connect to a particular Wi-Fi network in order to receive data from Wi-Fi signals being transmitted over that network because the network is a shared medium. According to aspects of the present disclosure, the Wi-Fi sensor may be configured to “sniff” the Wi-Fi transfers operating on various channels and extract information (e.g., SSID, MAC address, etc.) from the transfers without connecting to the network. In some embodiments, the Wi-Fi sensor may extract information such as SSID and MAC address from encrypted signals by locating the information within certain packets (management frames).

Proceeding to step 1304, particular Wi-Fi data may be received from a Wi-Fi sensor based on certain embodiment configurations. In one embodiment, the Wi-Fi data received may include at least the RSSI, MAC address, and SSID. In other embodiments, the Wi-Fi data may not include information such as SSID due to the network identification being concealed. Once the Wi-Fi data is received, the process may proceed to step 1306, where the RSSI is used to estimate proximity. According to aspects of the present disclosure, RSSI may be an indication of how close or far a device, such as a UAV, is to a particular signal source. The RSSI based on the particular signal may not be a definitive measure of location, but may be used as an indication of proximity.

At step 1308, the proximity estimated in step 1306 may be compared to an allowable proximity threshold. If it is determined that the RSSI from the Wi-Fi data is past the allowable threshold, then further action may need to be pursued, as will be described below. It should be understood from the discussion herein that the RSSI from a particular Wi-Fi signal may be interpreted in various ways. In one embodiment, a RSSI may be substantially low, indicating a weak signal. In some embodiments a weak signal may be interpreted as a threat because it may suggest that the controller is located some distance away and is aware of the limits of the network. In other embodiments, a strong RSSI may indicate that the source of the network is close by, and this may suggest that the network was recently established and potentially mobile, for example originating from hardware stored in a vehicle or from a mobile phone hot spot. However, the exemplary Wi-Fi data analysis process 1300 may be configured to disregard Wi-Fi signals resulting in RSSI's that are determined at step 1308 to not be past the allowable threshold, resulting in the process to jump to step 1314. In one embodiment, if it is determined that the estimated proximity is past the allowable threshold than the exemplary system 1300 proceeds to step 1310 where the MAC address and SSID information are analyzed both independently and as a combination.

In various embodiments, at step 1310 the MAC address from the received Wi-Fi data may be compared to various known MAC addresses stored in a database within the system, such as the Drone/UAV DNA and system management databases 412 and 414. According to aspects of the present disclosure, MAC addresses from known UAV manufacturers may be stored in a database 106 within the UAVTMS 102 or in a third party database 120. Consider an example where the MAC addresses of UAVs known to be manufactured from a popular UAV manufacturer such as 3D Robotics, Inc., are stored in a database 106 within the UAVTMS 102 or in a third party database 120. In certain embodiments, a UAV being controlled over Wi-Fi may be detected, and the MAC address may be compared the known stored MAC addresses. If the MAC addresses match or have fields of information that match the known MAC address information, this may indicate that the detected Wi-Fi signal is controlling a 3D Robotics UAV. In scenarios like the one described above, the exemplary process 1300 would proceed from step 1310 to step 1312 in order to make a decision based on a predetermined rule set. In one embodiment, if the MAC address from received Wi-Fi data is a strong indication of a UAV then a predetermined action may be exercising forceful action against the UAV such as jamming UAV signals and communications or disabling the UAV with a laser or projectile. In other embodiments, based on the MAC address of the detected UAV, it may be preferred to attempt to locate the source of the UAV controller. In some embodiments, the predetermined ruleset at step 1312 may assign a certain confidence level to the Wi-Fi data. If at step 1310 the MAC address was not recognized, the exemplary process 1300 may proceed to step 1314 where the system determines if it should continue to receive Wi-Fi signals.

Continuing with step 1310, analyzing the SSID may reveal the network identification. Similar to the storing of MAC addresses of known UAVs and UAV manufacturers, included in the database 106 of the UAVTMS 102, third party databases 120, or the Drone/UAV DNA and system management databases 412 and 414, may be a list of known SSID's. In certain embodiments, the stored SSID's may be SSID's that are trusted, not trusted, or a combination of both. According to aspects of the present disclosure, if at step 1310 it is determined that the SSID is recognized, then the exemplary process 1300 may proceed to step 1312 where a decision may be made according to a predetermined rule set. In one embodiment, step 1310 may also analyze the MAC address and SSID detected in the Wi-Fi data as a combination. According to aspects of the present disclosure, if both the MAC address and SSID detected in Wi-Fi data are indicative of UAV activity, this may also result in the process proceeding to step 1312 in order to make a decision based on a predetermined ruleset. Similar to the description of step 1312 above, this decision based on a predetermined rule set may include various actions such as forcefully engaging the UAV or attempting to locate the UAV controller. If at step 1310 is it determined that the SSID, MAC address, or a combination of the two are not recognized, then the exemplary process 1300 may continue to step 1314 where it is determined if the system should continue receiving Wi-Fi signals. In various embodiments, if it is determined that the system should continue to receive Wi-Fi signals, the exemplary process 1300 may proceed to step 1302 where the system may tune the Wi-Fi sensor to a different channel. If at step 1314 it is determined that the system should not continue to receive Wi-Fi signals, the exemplary process 1300 may terminate.

Turning now to FIG. 14 , a flowchart is shown illustrating the exemplary region of interest tracking process 1400. In one embodiment, the process may begin at step 1402 by receiving one or more regions of interest. Referring back to FIG. 7 , step 706 determines if regions of interest are identified in a video frame. If one or more regions of interest are present in the video frame than the one or more regions of interest may be forwarded to the exemplary region of interest tracking process 1400. In general, tracking regions of interest allows for the system to be able to determine where regions of interest are and where they are heading based on their current behavior. Also, the region of interest tracking process 1400 may allow for the system to rule out, or reject, certain regions of interest as potential UAVs based on certain behaviors. Once the exemplary region of interest tracking process 1400 receives one or more regions of interest at step 1402, the process may proceed to step 1404 where the process compares the sizes of the one or more regions of interest to the sizes of the same regions of interest as they were present in previous frames.

In various embodiments, the frame immediately previous to the current frame may include substantially similar regions of interest to the one or more regions of interest received at step 1402. In one embodiment, at step 1404 the current one or more regions of interest may be compared to the one or more previous regions of interest, and more specifically compared to the sizes of the regions of interest. In certain embodiments, if one or more regions of interest increase or decrease in size by a certain amount, percentage, or any appropriate method of measure, that increase or decrease may determine if the one or more regions of interest may be classified as UAVs. At step 1406, the size comparisons from step 1404 are further compared to certain configured thresholds. In some embodiments, the system may be configured to consider a sudden or substantial increase in size of one or more regions of interest uncharacteristic of a UAV, and then may determine that one or more regions of interest that exhibit that type of behavior are non-UAV. In other embodiments, the system may be configured to consider negligible or no change in size of one or more regions of interest also uncharacteristic of UAVs. In certain embodiments, an appropriate amount of change for one or more regions of interest may be within a certain threshold. If the amount of change of the one or more regions of interest is not within that threshold than the one or more regions of interest may be forwarded to and rejected at step 1408. In one embodiment, rejecting one or more regions of interest at step 1408 may include classifying the one or more regions of interest as non-UAV and further excluding the one or more regions of interest from further processing. If at step 1406 it is determined that the change in size of the one or more regions of interest is within an appropriate threshold, then the one or more regions of interest may be further compared to previous frames at step 1410.

In one embodiment, step 1410 may include comparing the one or more regions of interest currently being processed to the location of the one or more substantially similar regions of interest from previous frames. In certain embodiments, comparing the one or more regions of interest to the locations of one or more regions of interest from previous frames may provide an indication of the speed of the one or more regions of interest. More particularly and according to various aspects of the present disclosure, the center positions of the one or more regions of interest may be compared to the centers of the one or more regions of interest from previous frames.

At step 1412, it may be determined if the comparison of the positions of the one or more regions of interest to the one or more regions of interest from previous frames are within a certain threshold. In some embodiments, the result from comparing the one or more regions of interest to previous regions of interest may be a difference in pixels, or a calculated theoretical distance based on the changed position of the one or more regions of interest within the frame. If at step 1412 it is determined that the center positions of the one or more regions of interest have moved a certain amount within a certain threshold, then the process may continue to step 1414 where the speed of the one or more regions of interest are calculated. If at step 1412 it is determined that the center positions of the one or more regions of interest are not within an allowable threshold then the one or more regions of interest may be forwarded to and rejected at step 1408.

In one embodiment, at step 1414 the speed of the one or more regions of interest can be calculated based on the degree of movement between their current location within the frame and their locations in previous frames. In certain embodiments, calculating the speed of one or more regions of interest may allow for the system to better estimate and anticipate where a potential UAV may be in the area being monitored. According to aspects of the present disclosure, the speed of the one or more regions of interest, as well as the one or more regions of interest themselves, may be stored in a database, such as the database 106 of the UAVTMS 102, to be used for future reference. Proceeding to step 1416, in various embodiments, the one or more regions may be identified as tracked regions of interest. Referring back to FIG. 7 , if one or more regions of interest have been identified as tracked then they may proceed to the scene learning process 900. According to various aspects of the present disclosure, identifying an object as tracked does not guarantee that it will further be classified as a UAV. In various embodiments, identifying one or more regions of interest as tracked may allow for the one or more regions of interest to be further processed in the exemplary scene learning process 900. According to various aspects of the present disclosure, the steps 1414 and 1416 involving calculating the speed of one or more ROIs and identifying one or more ROIs as tracked may occur either simultaneously or interchangeably in order.

After either classifying one or more regions of interest as tracked at step 1416 or rejecting one or more regions of interest as possible UAVs at step 1408, the last step of the exemplary region of interest tracking process 1400 is step 1418, where it may be determined if there are more regions of interest to analyze. In various embodiments, if it is determined that there are additional regions of interest to analyze then the process may jump to step 1402 in order to receive one or more new regions of interest. If it is determined at step 1418 that there are no additional or new regions of interest to analyze then the exemplary region of interest tracking process 1400 may terminate.

Turning now to FIG. 15 , an exemplary airspace 1500 is shown illustrating a UAV 204 and a corresponding track 1502, according to one embodiment of the present disclosure. As discussed briefly above, a track generally includes a record of 3D coordinates (and other identifying information) relating to an object's prior locations in a 3D space, as detected by one or more sensors. For example, as shown in the present embodiment, the track 1502 includes a track point 1504A corresponding to a particular point in the airspace 1500 where the UAV 204 was detected. According to various aspects of the present disclosure, the track point 1504A may include data such as X, Y, and Z coordinates, a calculated/detected velocity of the UAV 204 (e.g., V₁), a time stamp relating to when the UAV 204 was detected (e.g., t₁), and other information such as any communication protocols, identification numbers, etc., that may have been detected. Furthermore, as the UAV 204 is detected in additional locations (e.g., as the UAV is “tracked”), the system may record/store additional track points, such as the track point 1504B, which may include 3D coordinates, a time stamp (e.g., t₂), a velocity (e.g., V₂), a calculated heading, etc., correspond to the newly detected UAV location.

In certain embodiments, recording track points may allow for the system to predict future track point locations. For example, the system may forecast a tracked object's future positions based on previously detected track coordinates, velocities, headings, etc. As shown in the present embodiment, a predicted track point 1506 may include predicted 3D coordinates, a predicted velocity, a predicted time of detection, etc. According to various aspects of the present disclosure, generating predicted track points may allow for the system to anticipate future locations of a tracked object and furthermore direct sensors, such as PTZ cameras, to adjust their orientations to best detect the tracked objects at these locations.

FIG. 16 is a flowchart of an exemplary radar track initialization process 1600, according to one aspect of the present disclosure. As discussed briefly above, the radar track initialization process 1600 may determine if received radar position readings are associated with known “tracks,” where a track corresponds to a series/collection of 3D locations in an airspace that a detected object is known to have previously occupied. Accordingly, a newly received radar position reading corresponding to a known track will likely be positioned near the head of the track, such that it would be reasonable and/or expected for the object to be positioned near the track head (given that the speed, acceleration, flight patterns, etc., of the tracked object are known, or can be calculated).

In one embodiment, at step 1602, the process 1600 begins when the system receives one or more position readings from the radar sensor. In various embodiments, each radar position reading is a point in three dimensional space, and may be represented as a set of coordinates (e.g., X, Y, and Z coordinates), or as another appropriate notation (e.g., a distance and angle). In particular embodiments, the system may continuously receive new radar sensor position readings, and the system may include any number of radar sensors. For example, the system may include radar sensors that generally scan wide areas of the monitored airspace, while other radar sensors are reserved or used for targeted monitoring.

At step 1604, and in certain embodiments, the system determines if the received radar position readings are nearby any preexisting tracks. According to various aspects of the present disclosure, the system may compare the locations of the one or more received position readings to one or more stored tracks, or to the heads of one or more stored tracks. In at least one embodiment, the system may include predetermined distance thresholds for determining if a radar position reading is nearby a preexisting track, where the thresholds at least consider the distance between the received radar position reading and an expected track head location, and a corresponding uncertainty/deviation. In a particular embodiment, if the one or more received position readings are substantially close to, or within an expected distance from, the heads of one or more stored tracks, the one or more received position readings may be determined to be associated with the tracks at step 1606. In certain embodiments, associating the one or more received position readings with a track may include appending or assigning the position readings to the track.

At step 1604, if there are no nearby tracks associated with the one or more received position readings, the process may proceed to step 1608 where the system creates a new “unverified” track. In one embodiment, creating a new unverified track may include instantiating a vector, array, or similar data object in computer memory for storing the 3D coordinates associated with the one or more position readings. In particular embodiments, the one or more position readings received at step 1602 may be included as the first position in the unverified track, or as a “tail,” in the track. In some embodiments, the radar sensor may receive a plurality of readings, although each reading may relate to one particular detected object. Thus, in at least one embodiment, the system may cluster these readings into a common unverified track, preventing the system from analyzing each reading independently and causing inefficiencies.

Furthermore, in some embodiments, the system may include tracks created in response to signals received by RF sensors or PTZ cameras. These tracks may already be verified as including a UAV. In these embodiments, and others, the one or more received radar position readings may be appended to the best fitting track and may not need further verification.

In one embodiment, the system may advance the tracks given the newly assigned positions at step 1610 after both steps 1606 and 1608. According to various aspects of the present disclosure, advancing the tracks may include predicting the most likely next track position, or an acceptable range for subsequent track positions, given the newly added position readings. In a particular embodiment, predicting future track positions may include generating a model based on the detected object velocity, acceleration, and flight pattern, and this may allow for the system to project where the track will likely be over time. In other embodiments, the model may also include data relating to known object behaviors, such as known UAV behaviors. Including known UAV behaviors in the model may allow for the system to determine if the detected objects are indicative of UAVs based on the detected track characteristics.

Continuing with FIG. 16 , the process 1600 may proceed to one or more sub-processes for verifying or classifying the object detected by the one or more radar position readings. In various embodiments, the system aims to determine if the object detected by the one or more radar position readings is a UAV. According to various aspects of the present disclosure, the process 1600 may proceed to the PTZ camera track verification process 1600, the exemplary RF data analysis process 1200, and/or other track verification processes, for visually verifying the tracked object (via PTZ cameras) or for determining if the tracked object is emitting or receiving RF signals indicative of known UAVs (via RF sensors). In particular embodiments, the system may also scan for audio signals indicative of UAV sounds/frequencies, Wi-Fi signals indicative of a UAV network connection, etc. However, in certain embodiments, the discussed sub-processes for track verification are exemplary and not each sub-process is required for verifying every track or received radar position reading.

In various embodiments, the process 1600 may proceed to step 1612, where the unverified tracks or track positions are verified based on an aggregated confidence measure resulting from the one or more sub-processes for verifying/classifying the object. According to various aspects of the present disclosure, the aggregated confidence measure may be compared to a predetermined threshold, where the predetermined threshold may be a percentage, such as 80%, 85%, 90%, etc., indicating the likelihood that the unverified tracks indeed do include a UAV and should be denoted as verified within the system.

Proceeding now to step 1614, in one embodiment, the system takes action based on the verified tracks. In a particular embodiment, the system notifies the system user regarding the verified tracks. In various embodiments, the notification may include an audio alert and/or a visual alert presented on a computing device. The alert may include information such as the verified UAV's location, speed, potential risk, video evidence of the UAV, etc., which may allow for the user to determine how to react to the UAV. In certain embodiments, the system may perform any appropriate action in response to verifying the tracks, such as jamming the corresponding UAV communications, forcefully downing the UAV (e.g., via a projectile, a laser, etc.), closing rooftops (e.g., in a sports area, in a prison, etc.), concealing sensitive equipment (e.g., near a military base), initiating additional processes, etc. In various embodiments, the process may terminate after step 1614.

In one embodiment, FIG. 17 is a flowchart of an exemplary PTZ camera track verification process 1700. PTZ cameras, or “pan, tilt, and zoom” cameras, generally include image capturing devices capable of remote directional and zoom control. In various embodiments, the PTZ cameras discussed herein may operate similarly to the LZV2925B model camera manufactured and sold by Lorex Technology, and other makes/models as well. In other embodiments, the PTZ cameras discussed herein may operate similarly to the Q8685-E PTZ Network Camera manufactured by Axis Communications in Lund, Sweden, and also to the CM202U manufactured by Ascent Vision in Belgrade, Mont., U.S. In general, the PTZ cameras discussed herein may each detect more than one object (e.g., a UAV) at once, however, tracking more than one object with a single PTZ camera presents difficulties if the detected objects begin to diverge in different directions or if one or more objects block a line of site to another object. Accordingly, in one embodiment, the PTZ cameras described in the present disclosure are typically assigned to one track for monitoring and following the object associated with the track. However, in some embodiments, the PTZ cameras may engage in a “handshake” process, where an object being tracked by a first PTZ camera may be assumed by a second PTZ camera, if the second PTZ camera is determined to be more equipped for tracking the object (e.g., if the object travels away from an optimal range of the first PTZ camera into an optimal range of the second PTZ camera).

In various embodiments, the process 1700 may begin by executing the PTZ camera assignment process 1800. As will be described in greater detail below in association with FIG. 18 , the PTZ camera assignment process 1800 analyzes the tracks currently monitored by the system and determines which PTZ camera in the system is best fit for monitoring the track.

In response to assigning PTZ cameras to their best fit track at the process 1800, the process 1700 may proceed to step 1702, where the system directs the selected PTZ to the predicted position of the corresponding track. According to various aspects of the present disclosure, a PTZ camera may receive the 3D coordinate of the predicted position of the assigned track and configure it's orientation to be directed towards the predicted location. In particular embodiments, the system may convert the 3D coordinate into instructions that may be directly implemented by the PTZ camera, such as an instruction for a motor to be engaged for 5 milliseconds which may direct the PTZ orientation appropriately. In at least one embodiment, the most likely position of the track, and most likely size of the object in the track, are both estimated under the assumption that the object is indeed a UAV, and if the position of the track is uncertain then the system may randomly sample a potential UAV position near the most likely position predicted according to the track trajectory. In various embodiments, in response to the PTZ camera being directed in the position of the predicted track position, the PTZ camera may capture video and/or image frames at the predicted track position to be processed at the video data analysis process 700. In at least one embodiment, the system may configure the PTZ zoom (and other configurations) such that the camera captures the least amount of pixels possible for verifying a UAV in a track. In various embodiments, directing the PTZ cameras may include instructing the PTZ cameras to pan, tilt, and/or zoom with respect to the predicted position of each assigned track such that the tracks are “followed” over time.

In a particular embodiment, the video data analysis process 700 may indicate if the tracks followed by the PTZ cameras include a UAV. In various embodiments, at step 1704 it is determined that if a UAV is identified within the track, the process may proceed to the PTZ tracking process 1800. If a UAV is not identified, at step 1704, the process may proceed to the step 1706, where the system updates a time counter recording the time spent on the track verification. According to various aspects of the present disclosure, the system may track the time spent on attempted track verification. In certain embodiments, recording the time spent on verifying tracks via PTZ (and other sensors) may allow for the system to determine if it is taking too long to verify a track, which may indicate that the track does not include a UAV. For exemplary purposes only, if it generally takes the system about one millisecond to determine if a track includes a UAV, then if the system has taken over one second to determine if a track includes a UAV, it most likely does not include a UAV and the system may reassign the PTZ camera to another track. In a particular embodiment, further description relating to recording time spent verifying tracks is discussed below in association with FIG. 18 .

In one embodiment, FIG. 18 is a flowchart of the exemplary PTZ assignment process 1800. As will be described in greater detail immediately below, the PTZ assignment process 1800 includes various steps for evaluating aspects of identified tracks for determining how the PTZ cameras should be assigned to the identified tracks. In various embodiments, the process 1800 may begin at step 1802 where the system receives data relating to one or more tracks (e.g., a set of 3D coordinates), or retrieves the data relating to the one or more tracks from a stored location (e.g., cache, memory, a database, etc.).

In particular embodiments, in response to receiving the data relating to the one or more tracks, the process 1800 may proceed to a series of steps for evaluating the track data, and the system may perform each of the series of steps before assigning a PTZ camera to a track, or the system may perform only a select one or few of the steps. In at least one embodiment, the step 1804 includes evaluating the track data for a user-selected priority. According to various aspects of the present disclosure, if the user of the system selects a particular track to be visually verified, the selected track may be assigned the nearest PTZ, which may then immediately search for the object in the airspace (e.g., the user-selected track is prioritized over other tracks).

In one embodiment, for optimization purposes, the system may verify as many unverified tracks as possible (e.g., the system reduces resources spent monitoring non-UAVs). Accordingly, in various embodiments, unverified tracks may receive priority, or a bias, when assigning PTZ camera to tracks. Thus, at step 1806, the system may evaluate unverified tracks for this bias/priority for determining PTZ assignments (e.g., newly identified tracks with only radar position readings may receive an initial bias).

In particular embodiments, at step 1808, the system may evaluate the time spent on individual tracks. In general, the system aims to minimize the time expenditure for verifying all UAVs in an airspace. Therefore, in particular embodiments, the system may assign a PTZ camera to a track with a lower average spent time than another track, which is less likely to include a UAV.

In certain embodiments, the system may evaluate the uncertainty associated with a track's predicted position. As mentioned above in the discussion associated with step 1610 of FIG. 16 , the system advances the tracks in response to newly assigned positions. According to various aspects of the present disclosure, and at step 1810 of FIG. 18 , the system may further evaluate the predicted position for an uncertainty. In one embodiment, if the predicted position is generally close to the track head, and is within a generally small area, the track may be evaluated with a “high” certainty. In a particular embodiment, a “high certainty” may be also determined by an aggregated confidence level above about 70%, or may be determined by a small pixel variance from a predicted location within a frame (e.g., 1, 2, 3 pixels, etc., off center from a predicted location). In some embodiments, tracks with higher certainties may be assigned certain PTZ cameras before or over other tracks to increase the likelihood of verifying UAVs within the tracks.

According to various aspects of the present disclosure, the uncertainty of a predicted track location may further be determined based on factors such as: (1) variance between a model of plausible track positions (based on a Kalman filter), and (2) a calculated standard deviation based on position measurements from each sensor monitoring the track. Generally, a track of a “high certainty” is produced when a detected object moves like a drone according to the system's Kalman filter model, and is within a predetermined distance (e.g., 50 m, 75 m, 100 m, etc.) from a PTZ camera, where if the tracked object is within this distance then the system may verify the object/track as a UAV with reasonably high probability (e.g., about 70%) due to high resolution image capturing from the PTZ camera. In one embodiment, a track of a “high certainty” is determined when the predicted track location is with a certain standard deviation of the current position measurements, and the predicted track location is within 50 m of the current position measurements.

In at least one embodiment, and at step 1812, the system may evaluate the proximities of the identified tracks to the PTZ cameras. For example, in a certain embodiment, if a particular received track is nearby or within an optimal range of a particular PTZ camera, that particular track may receive a higher value, priority, or bias, than other tracks for being assigned to that particular PTZ camera. In other embodiments, at step 1814, the system may evaluate other track metrics. For example, if a particular track is detected at a substantially high elevation, the track may receive priority to be assigned to a PTZ camera with stronger zoom capability than the other PTZ cameras.

In one embodiment, in response to appropriately evaluating the one or more received tracks for PTZ camera assignment based on the various aspects of the tracks (steps 1804-1814), at step 1816 the system may assign the one or more PTZ cameras to the tracks, where the PTZ cameras furthermore automatically follow their assigned tracks for collecting video/image frames for determining if the tracks include a UAV (e.g., verifying the tracks).

FIG. 19 is a flowchart illustrating an exemplary PTZ camera tracking process 1900, according to one aspect of the present disclosure. In at least one embodiment, in response to the PTZ cameras being assigned to tracks (process 1800) and being directed to the predicted positions of the assigned tracks (step 1702 in process 1700), the PTZ cameras may continuously update their orientations for maintaining focus on the tracks verified as including a UAV. Accordingly, in various embodiments, the process 1900 may begin at step 1902 where the system receives one or more frames from a PTZ camera. According to various aspects of the present disclosure, the frames may be received as an array or matrix of pixel values (e.g., RGB pixel values), where each pixel value corresponds to a particular color in the frame captured by the PTZ camera.

In at least one embodiment, the process may proceed to step 1904, where the system performs object detection techniques on the one or more frames specifically for identifying UAVs, thus allowing the system to better follow the UAVs. According to various aspects of the present disclosure, the object detection techniques may include applying a neural network that has been trained for processing one or more image frames for identifying UAVs in an airspace, as well as for detecting objects that are easily confused with UAVs, within the frame. The neural network may be trained by using training data including historical images or streams with known successfully identified UAVs and erroneously identified UAVs. In a particular embodiment, the output from step 1804 may include one or more bounding boxes for encompassing the UAV (or other objects) within the frame, as well as one or more confidence scores indicative of the likelihood that the objects included in the bounding boxes are UAVs. For example, a PTZ captured frame processed at step 1904 may include both a UAV and a bird, and the system may recognize both as objects (or ROIs) within the frame to be encompassed with bounding boxes. The UAV included in the bounding box may be assigned an almost certain confidence score (e.g., 99%) in response to the UAV-specific object detection algorithms, while the bird may receive a lower confidence score (e.g., 5%), and thus the bird may be dismissed as a non-drone or non-UAV.

At step 1906, and according to one embodiment, the system determines if one or more UAVs are identified within the received PTZ video frame. In a particular embodiment, the system may be configured to evaluate a confidence measure indicative of how likely the object is indeed a UAV, and how likely the object is not one of the objects that are easily confused with UAVs. Furthermore, the confidence measure may consider if the detected objects lie within an attention region where a UAV is expected to be identified. At step 1906, if one or more UAVs are not identified, the process may terminate. However, if at step 1906, one or more UAVs are identified within the frame, the process may proceed to step 1908, where the system controls the PTZ cameras to center the detected UAV in the camera's field of view (to adjust for the UAV's movement and predicted movement). In various embodiments, the system may apply a PID controller-based command so that the PTZ may perform a smooth, continuous motion for adjusting its direction to maintain the UAV centered within the PTZ frame.

From the foregoing, it will be understood that various aspects of the processes described herein are software processes that execute on computer systems that form parts of the system. Accordingly, it will be understood that various embodiments of the system described herein are generally implemented as specially-configured computers including various computer hardware components and, in many cases, significant additional features as compared to conventional or known computers, processes, or the like, as discussed in greater detail herein. Embodiments within the scope of the present disclosure also include computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable media can be any available media which can be accessed by a computer, or downloadable through communication networks. By way of example, and not limitation, such computer-readable media can comprise various forms of data storage devices or media such as RAM, ROM, flash memory, EEPROM, CD-ROM, DVD, or other optical disk storage, magnetic disk storage, solid state drives (SSDs) or other data storage devices, any type of removable non-volatile memories such as secure digital (SD), flash memory, memory stick, etc., or any other medium which can be used to carry or store computer program code in the form of computer-executable instructions or data structures and which can be accessed by a computer.

When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such a connection is properly termed and considered a computer-readable medium. Combinations of the above should also be included within the scope of computer-readable media. Computer-executable instructions comprise, for example, instructions and data which cause a computer to perform one specific function or a group of functions.

Those skilled in the art will understand the features and aspects of a suitable computing environment in which aspects of the disclosure may be implemented. Although not required, some of the embodiments of the claimed inventions may be described in the context of computer-executable instructions, such as program modules or engines, as described earlier, being executed by computers in networked environments. Such program modules are often reflected and illustrated by flow charts, sequence diagrams, exemplary screen displays, and other techniques used by those skilled in the art to communicate how to make and use such computer program modules. Generally, program modules include routines, programs, functions, objects, components, data structures, application programming interface (API) calls to other computers whether local or remote, etc. that perform particular tasks or implement particular defined data types, within the computer. Computer-executable instructions, associated data structures and/or schemas, and program modules represent examples of the program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represent examples of corresponding acts for implementing the functions described in such steps.

Those skilled in the art will also appreciate that the claimed and/or described systems and methods may be practiced in network computing environments with many types of computer system configurations, including personal computers, smartphones, tablets, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, networked PCs, minicomputers, mainframe computers, and the like. Embodiments of the claimed invention are practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination of hardwired or wireless links) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

An exemplary system for implementing various aspects of the described operations, which is not illustrated, includes a computing device including a processing unit, a system memory, and a system bus that couples various system components including the system memory to the processing unit. The computer will typically include one or more data storage devices for reading data from and writing data to. The data storage devices provide nonvolatile storage of computer-executable instructions, data structures, program modules, and other data for the computer.

Computer program code that implements the functionality described herein typically comprises one or more program modules that may be stored on a data storage device. This program code, as is known to those skilled in the art, usually includes an operating system, one or more application programs, other program modules, and program data. A user may enter commands and information into the computer through keyboard, touch screen, pointing device, a script containing computer program code written in a scripting language or other input devices (not shown), such as a microphone, etc. These and other input devices are often connected to the processing unit through known electrical, optical, or wireless connections.

The computer that affects many aspects of the described processes will typically operate in a networked environment using logical connections to one or more remote computers or data sources, which are described further below. Remote computers may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically include many or all of the elements described above relative to the main computer system in which the inventions are embodied. The logical connections between computers include a local area network (LAN), a wide area network (WAN), virtual networks (WAN or LAN), and wireless LANs (WLAN) that are presented here by way of example and not limitation. Such networking environments are commonplace in office-wide or enterprise-wide computer networks, intranets, and the Internet.

When used in a LAN or WLAN networking environment, a computer system implementing aspects of the invention is connected to the local network through a network interface or adapter. When used in a WAN or WLAN networking environment, the computer may include a modem, a wireless link, or other mechanisms for establishing communications over the wide area network, such as the Internet. In a networked environment, program modules depicted relative to the computer, or portions thereof, may be stored in a remote data storage device. It will be appreciated that the network connections described or shown are exemplary and other mechanisms of establishing communications over wide area networks or the Internet may be used.

While various aspects have been described in the context of a preferred embodiment, additional aspects, features, and methodologies of the claimed inventions will be readily discernible from the description herein, by those of ordinary skill in the art. Many embodiments and adaptations of the disclosure and claimed inventions other than those herein described, as well as many variations, modifications, and equivalent arrangements and methodologies, will be apparent from or reasonably suggested by the disclosure and the foregoing description thereof, without departing from the substance or scope of the claims. Furthermore, any sequence(s) and/or temporal order of steps of various processes described and claimed herein are those considered to be the best mode contemplated for carrying out the claimed inventions. It should also be understood that, although steps of various processes may be shown and described as being in a preferred sequence or temporal order, the steps of any such processes are not limited to being carried out in any particular sequence or order, absent a specific indication of such to achieve a particular intended result. In most cases, the steps of such processes may be carried out in a variety of different sequences and orders, while still falling within the scope of the claimed inventions. In addition, some steps may be carried out simultaneously, contemporaneously, or in synchronization with other steps.

The embodiments were chosen and described in order to explain the principles of the claimed inventions and their practical application so as to enable others skilled in the art to utilize the inventions and various embodiments and with various modifications as are suited to the particular use contemplated. Alternative embodiments will become apparent to those skilled in the art to which the claimed inventions pertain without departing from their spirit and scope. Accordingly, the scope of the claimed inventions is defined by the appended claims rather than the foregoing description and the exemplary embodiments described therein. 

What is claimed is:
 1. A system for identifying unmanned aerial vehicles (UAVs) in a particular airspace, comprising: a radar sensor configured to monitor the particular airspace; a plurality of image capturing devices configured to monitor the particular airspace; and a server comprising a processor, wherein the server is operatively connected to the radar sensor and the plurality of image capturing devices, and wherein the processor is operative to: receive signal readings from the radar sensor, wherein the signal readings comprise location data corresponding to one or more objects detected in the particular airspace via the radar sensor; compare the received signal readings to a plurality of historical readings, wherein the plurality of historical readings correspond to known object trajectories detected within the particular airspace, and wherein each of the plurality of historical readings comprises a predicted location of an object and an acceptable location uncertainty corresponding to a subsequent object location; upon determining that a particular reading of the received signal readings comprises location data substantially similar to the predicted location of a matching historical reading and is within the acceptable location uncertainty corresponding to the matching historical reading, associate the particular reading with the matching historical reading; calculate a new predicted location for the matching historical reading in response to associating the particular reading with the matching historical reading; reorient the radar sensor based on the new predicted location; determine that an elapsed time spent verifying a track based on the received signal readings meets a threshold; and in response to determining that the elapsed time spent verifying the track meets a threshold, prioritize analyzing at least one different track over the track.
 2. The system of claim 1, wherein associating comprises adding the particular reading to the matching historical reading.
 3. The system of claim 1, wherein the processor is further operative to determine, for the matching historical reading, a particular image capturing device of the plurality of image capturing devices to be assigned to the matching historical reading, wherein determining comprises evaluating at least the location data corresponding to the matching historical reading to locations of each of the plurality of image capturing devices.
 4. The system of claim 3, wherein the processor is further operative to direct the particular image capturing device to monitor the particular airspace corresponding to the location data of the matching historical reading.
 5. The system of claim 4, wherein the processor is further operative to receive image data from the particular image capturing device, wherein the image data depicts the particular airspace corresponding to the location data for verifying the one or more objects as UAVs.
 6. The system of claim 4, wherein the processor directs the particular image capturing devices via a proportional-integral-derivative (“PID”) controller.
 7. The system of claim 6, wherein the PID controller is adjusted at about 30 cycles per second.
 8. The system of claim 5, wherein the processor is further operative to perform an object detection process in response to receiving the image data.
 9. The system of claim 1, wherein the plurality of historical readings are associated with the track comprising a record of three-dimensional coordinates corresponding to the known object trajectories detected within the particular airspace, and the predicted location of the object.
 10. The system of claim 9, wherein each of the plurality of historical readings comprises a timer for recording time spent verifying the one or more objects as UAVs.
 11. The system of claim 10, wherein determining assignments comprises evaluating the timer at the matching historical reading.
 12. The system of claim 1, wherein each of the image capturing devices comprise pan-tilt-zoom (“PTZ”) cameras.
 13. A method for identifying unmanned aerial vehicles (UAVs) in a particular airspace via a processor at a server, wherein the server is operatively connected to a radar sensor configured to monitor the particular airspace, and operatively connected to a plurality of image capturing devices configured to monitor the particular airspace, the method comprising the steps of: receiving signal readings from the radar sensor, wherein the signal readings comprise location data corresponding to one or more objects detected in the particular airspace via the radar sensor; comparing the received signal readings to a plurality of historical readings, wherein the plurality of historical readings correspond to known object trajectories detected within the particular airspace, and wherein each of the plurality of historical readings comprises a predicted location of an object and an acceptable location uncertainty corresponding to a subsequent object location; upon determining that a particular reading of the received signal readings comprises location data substantially similar to the predicted location of a matching historical reading and is within the acceptable location uncertainty corresponding to the matching historical reading, associating the particular reading with the matching historical reading; calculating a new predicted location for the matching historical reading in response to associating the particular reading with the matching historical reading; reorienting the radar sensor based on the new predicted location; determining that a time verifying a track based on the received signal readings meets a threshold; and in response to determining that the time verifying the track meets a threshold, prioritizing analyzing at least one different track over the track.
 14. The method of claim 13, wherein associating comprises adding the particular reading to the matching historical reading.
 15. The method of claim 13, further comprising the step of determining, for the matching historical reading, a particular image capturing device of the plurality of image capturing devices to be assigned to the matching historical reading, wherein determining comprises evaluating at least the location data corresponding to the matching historical reading to locations of each of the plurality of image capturing devices.
 16. The method of claim 15, further comprising the step of directing the particular image capturing device to monitor the particular airspace corresponding to the location data of the matching historical reading.
 17. The method of claim 16, further comprising the step of receiving image data from the particular image capturing device, wherein the image data depicts the particular airspace corresponding to the location data for verifying the one or more objects as UAVs.
 18. The method of claim 16, wherein the processor directs each of the particular image capturing device via a proportional-integral-derivative (“PID”) controller.
 19. The method of claim 18, wherein the PID controller is adjusted at about 30 cycles per second.
 20. The method of claim 17, wherein the processor is further operative to perform an object detection process in response to receiving the image data.
 21. The method of claim 13, wherein the plurality of historical readings are associated with the track comprising a record of three-dimensional coordinates corresponding to the known object trajectories detected within the particular airspace, and the predicted location of the object.
 22. The method of claim 21, wherein each of the plurality of historical readings comprises a timer for recording time spent verifying the one or more objects as UAVs.
 23. The method of claim 22, wherein determining assignments comprises evaluating the timer at the matching historical reading.
 24. The method of claim 13, wherein each of the image capturing devices comprise pan-tilt-zoom (“PTZ”) cameras.
 25. The method of claim 13, wherein the acceptable location uncertainty is about 70% certain.
 26. The system of claim 3, wherein the processor is further operative to reorient the particular image capturing device to monitor the particular airspace corresponding to the new predicted location. 